-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
npm ERR while resolving [email protected] #7095
Comments
This has started causing issues for us with the new node version The workaround for us was to downgrade node to |
It looks like some work is happening on this in #6323 but there hasn't been any progress for almost a year. |
@aethr thank you for the work around. for anyone else suck with this in docker, node version 16.15-apline and its 3.15, 3.16 variants did not work for me, i ended up forcing the container to my local version:
|
In Netlify you can luckily set the node version as an environment variable, which now works with |
Can't reproduce. |
As for @frankykubo's project, I see that your envinfo doesn't match your |
When I do that with latest vue dependencies it breaks soursmaps from what
looks like babel issue.
I'll post my config later today when I return to my office and we can
compare his config and mine. I'll see if I can recreate without a
package-lock as well.
…On Mon, Jun 20, 2022, 8:59 AM Haoqun Jiang ***@***.***> wrote:
As for @frankykubo <https://github.com/frankykubo>'s project, I see that
your envinfo doesn't match your package-lock.json. There are multiple
versions of the same package in your envinfo (e.g. @vue/cli-plugin-babel:
^5.0.4 => 5.0.4 (4.5.4), indicating that v5.0.4 and v4.5.4 co-exist in
your project). I guess removing package-lock.json, node_modules and
reinstalling the dependencies would help.
—
Reply to this email directly, view it on GitHub
<#7095 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEJUAEFVVBL4GFRHO4NHSUDVQBTMVANCNFSM5SVDH3DA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
In my case I eneded up having to down grade from the latest version of TS to get source map outputs again. After which deleting the package-lock.json file solved the issue here. |
So I was running into this issue trying to upgrade from @vue/cli-plugin-typescript 5.0.4 to 5.0.8. I don't know if this will help anyone but I was able to upgrade by upgrading the version in the package.json and then running |
This commit fixes two issues: a. Fix `npm install` not working b. Fix building not working after npm install fix. npm install fails with dependency resolution issue due to Vue CLI as following: ```txt npm ERR! code ERESOLVE npm ERR! ERESOLVE could not resolve npm ERR! npm ERR! While resolving: [email protected] ... ```txt As suggested in Vue issues regenerating packages-lock.json solves the issue, see: vuejs/vue-cli#6793, vuejs/vue-cli#7095. However with the new package-lock.json a Font Awesome dependency issue breaks the builds such as the following: ```txt ERROR in src/presentation/bootstrapping/Modules/IconBootstrapper.ts:17:7 TS2345: Argument of type 'IconDefinition' is not assignable to parameter of type 'IconDefinitionOrPack'. Type 'IconDefinition' is not assignable to type 'IconPack'. Index signature for type 'string' is missing in type 'IconDefinition'. 15 | public bootstrap(vue: VueConstructor): void { 16 | library.add( > 17 | faGithub, ``` This is solved by adding a patch in `tsconfig.json`. This issue was discussed in FortAwesome/Font-Awesome#12575 where the workaround was recommended.
This commit fixes two issues: a. Fix `npm install` not working b. Fix building not working after npm install fix. npm install fails with dependency resolution issue due to Vue CLI as following: ```txt npm ERR! code ERESOLVE npm ERR! ERESOLVE could not resolve npm ERR! npm ERR! While resolving: [email protected] ... ```txt As suggested in Vue issues regenerating packages-lock.json solves the issue, see: vuejs/vue-cli#6793, vuejs/vue-cli#7095. However with the new package-lock.json a Font Awesome dependency issue breaks the builds such as the following: ```txt ERROR in src/presentation/bootstrapping/Modules/IconBootstrapper.ts:17:7 TS2345: Argument of type 'IconDefinition' is not assignable to parameter of type 'IconDefinitionOrPack'. Type 'IconDefinition' is not assignable to type 'IconPack'. Index signature for type 'string' is missing in type 'IconDefinition'. 15 | public bootstrap(vue: VueConstructor): void { 16 | library.add( > 17 | faGithub, ``` This is solved by adding a patch in `tsconfig.json`. This issue was discussed in FortAwesome/Font-Awesome#12575 where the workaround was recommended.
Version
5.0.4
Reproduction link
github.com
Environment info
Steps to reproduce
What is expected?
Successful npm install
What is actually happening?
The text was updated successfully, but these errors were encountered: