-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Critical] - Build is failing. Missing dependency nuxt-property-decorator #44
Comments
Looks like my bugfix was merged in. Once David publishes the changes, this issue should be fixed. 🎉 |
But what exactly you've changed? Is it only the version number in package.json? |
Yes, this is the version number that DavidBernal published with the fix to this issue. This issue was the fault of nuxt-property-decorator not publishing the file defined in the |
I am still getting this error
Even when I install Any clues on how to fix ?
EDIT: Just to add, I was running the dev to see the output. Not run build |
In |
@DevinZhong Thanks. Will give that a go and report back 😺 |
@DevinZhong it's not really a fix for the issue. The only way this issue can be resolved is by fixing nuxt-property-decorator |
@AndrewBogdanovTSS is right, project will compile with this fix, but will fail in runtime. |
@AndrewBogdanovTSS oh, yes, you're right! It failed in runtime finally. Forgive my carelessness. |
So, we are still no further forward ? |
Someone needs to take ownership of nuxt-property-decorator. Current owner is unable to support it further. @Atinux maybe you could take it under your wing? |
Used
Definately seems to be a problem with that package but not sure what. |
That should help? Would there be any reason not to do this? Still would require whatever changed from 1.1.3 -> 1.1.4 to be rolled back / fixed... |
Just stumbled upon this issue too. |
@RaZeR-RBI Did not drop the version that far but will give it a go. |
Getting a different error now. This is also with or without the nuxt-property-decorator (IE, it makes no difference if there or not)
|
I managed to get it working by using
|
Hi @timrijkse - I run into that, too. Try replacing I'm not sure why that has been changed / added. |
Is there an ETA for a fix for this, now that you've taken over nuxt-property-decorator @breakingrobot @Atinux? |
@moritzsternemann If you have clue or a PR, I'll review it and merge it 👍 |
I created nuxt-community/nuxt-property-decorator#10 to go on from there. Couldn't figure out what exactly the problem is... |
各位大佬加油修复bug啊~~~ |
This dependency was not found:
* nuxt-property-decorator in ./node_modules/ts-loader?{"appendTsSuffixTo":[{}]}!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./compon
ents/Card.vue, ./node_modules/ts-loader?{"appendTsSuffixTo":[{}]}!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./pages/index.vue
To install it, you can run: npm install --save nuxt-property-decorator $ cat ./node_modules/nuxt-property-decorator/package.json | grep version
"version": "1.1.4",
$ tree ./node_modules/nuxt-property-decorator
./node_modules/nuxt-property-decorator
├── lib
│ ├── nuxt-property-decorator.d.ts
│ └── nuxt-property-decorator.js
├── LICENSE
├── package.json
└── README.md package.json "main": "lib/nuxt-property-decorator.umd.js",
"scripts": {
"build": "tsc -p src/tsconfig.json && npm run build:umd",
"build:umd": "rollup -c",
}, File Seems like command With locally builded can check by: $ yarn add makyo-dev/nuxt-property-decorator |
@timrijkse @hartmut-co-uk the |
This is fixed as of |
Steps to reproduce:
Clone repo using vue-cli
Install dependency with npm/yarn
Run npm run dev
ERROR Failed to compile with 2 errors12:32:38
This dependency was not found:
To install it, you can run: npm install --save nuxt-property-decorator
nuxt-property-decorator is present in node_modules folder, but it seems that it's broken. It references some unexistent entry point in package.json nuxt-property-decorator.umd
I have strong doubts on whether it should be used instead of nuxt-class-component + vue-property-decorator although it seems logical, the dependency itself is quite problematic
The text was updated successfully, but these errors were encountered: