-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Failed to use Primevue 4 with yarn #6020
Comments
Interesting! I couldn't replicate it. Could you please attach a sample project with your config? |
same for the using nuxt with pnpm. |
Hmm, this problem might be related to 'peerDependencies'. The '@primeuix/styled' dependency in |
i'm using
in my .npmrc maybe related with these config. i will try without this config and i keep here updated. |
Thanks @antlionguard ;) |
I used the settings from @antlionguard without any effect. Additional information:
I have a simple playground project which I wanted to use for reproduction - an I failed, the application can be built. But the output of When I look in to the node_modules/@primeuix directory, I find a very different setting: In the application which fails:
In the playground project:
What I did to reproduce the effect:
=> produces 45 errors.
=> Everything is ok! |
Thank you so much, @ancasicolica ;) This really helped me. Fixed for the next version. |
Thanks a lot @mertsincan , this was a first class support handling! |
Describe the bug
Upgraded my projects from PrimeVue 3 to 4. When using yarn (v4.3.1) as packet manager I can't build my webapps having several errors. When using npm instead, no errors occur, everything is ok. Not sure whether this is a PrimeVue or yarn bug, reporting it here as yarn is mentioned as one of the means for installing PrimeVue.
Reproducer
none (not applicable)
PrimeVue version
4.0.0
Vue version
3.x
Language
ES6
Build / Runtime
Vue CLI App
Browser(s)
n/a
Steps to reproduce the behavior
Expected behavior
Using yarn should have the same effect as npm
The text was updated successfully, but these errors were encountered: