-
Notifications
You must be signed in to change notification settings - Fork 33
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
Peer dependency problem #28
Comments
Hi, Is by any chance, one of them is a dependency and the other is a devDependency? |
No, both of them are dependencies. I also tried moving them both to devDependency, but got the same error. |
Can you provide us a package json that makes this error? I'll use it as a test case for a unit test, to make sure it passes your sample after the fix. |
Sure thing, here's the exact package.json file:
|
Hi there! In the end I uninstalled the package, because I just used it in a very part of my code. But interestingly, this dependency problem wasn't the reason why my docker build crashed - it was a problem with node. After downgrading to node:14.13.1-alpine3.12, I was able to successfully build my docker container. Just leaving the info here, if anybody else has a similar problem. |
Hello there. I'm experiencing a problem with a npm WARN like this:
npm WARN [email protected] requires a peer of @vue/composition-api@>= 0.4.0 but none is installed. You must install peer dependencies yourself.
While this is not a problem for a local development, as it only displays a warning, this actually crashes my docker build and application deployment. Is there any fix for this? I do have newest vuex-composition-helpers and @vue/composition-api packages installed as dependencies, so I don't understand where's this warning coming from?
The exact error log from docker looks like this:
The text was updated successfully, but these errors were encountered: