[Bug]: npm install failed

[christillman]

Description

Directly after installing node.js on my recently installed Windows 11 machine, I navigated to the issue-forms-creator folder where I cloned your project. There I used npm install and got the errors below. Some dependencies don't work now?

Minimal Reproduction

Tried again, same result

Exception or Error

PS C:\EncounterPro\angular\issue-forms-creator> npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @angular-eslint/[email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/cli
npm ERR! dev @angular/cli@"^14.2.6" from the root project
npm ERR! peerOptional @angular/cli@">=6.0.0" from @storybook/[email protected]
npm ERR! node_modules/@storybook/angular
npm ERR! dev @storybook/angular@"^6.5.12" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/cli@">= 13.0.0 < 14.0.0" from @angular-eslint/[email protected]
npm ERR! node_modules/@angular-eslint/schematics
npm ERR! dev @angular-eslint/schematics@"13.2.1" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @angular/[email protected]
npm ERR! node_modules/@angular/cli
npm ERR! peer @angular/cli@">= 13.0.0 < 14.0.0" from @angular-eslint/[email protected]
npm ERR! node_modules/@angular-eslint/schematics
npm ERR! dev @angular-eslint/schematics@"13.2.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! C:\Users\Somebody\AppData\Local\npm-cache_logs\2023-06-17T03_43_17_725Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Somebody\AppData\Local\npm-cache_logs\2023-06-17T03_43_17_725Z-debug-0.log

[geromegrignon]

Hello Christopher, for a quick fix on your side, you can run nom install with --force. On my latest dependancy update, I missed the eslint part to match angular core version. However forcing installation with a different eslint version will still work.

[christillman]

Thanks for the quick response! FYI, below are the other warnings emitted with --force. I'm new to angular, but it seems the project moves so fast that it's a full time job just keeping up! With what I have done with angular already, in my day job, it has really impressed me. My project here, EncounterPro_OS, is built in Powerbuilder but I think I would like to start rewriting it in angular as a way forward to the future. PS C:\EncounterPro\angular\issue-forms-creator> npm install --force npm WARN using --force Recommended protections disabled. npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: @***@***.*** npm WARN Found: @***@***.*** npm WARN ***@***.***/cli npm WARN dev @angular/cli@"^14.2.6" from the root project npm WARN 1 more ***@***.***/angular) npm WARN npm WARN Could not resolve dependency: npm WARN peer @angular/cli@">= 13.0.0 < 14.0.0" from @***@***.*** npm WARN ***@***.***/schematics npm WARN dev @angular-eslint/schematics@"13.2.1" from the root project npm WARN npm WARN Conflicting peer dependency: @***@***.*** npm WARN ***@***.***/cli npm WARN peer @angular/cli@">= 13.0.0 < 14.0.0" from @***@***.*** npm WARN ***@***.***/schematics npm WARN dev @angular-eslint/schematics@"13.2.1" from the root project npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: ***@***.*** npm WARN Found: ***@***.*** npm WARN ***@***.***/schematics-core/node_modules/inquirer npm WARN inquirer@"7.0.3" from @***@***.*** npm WARN ***@***.***/schematics-core npm WARN @schuchard/schematics-core@"^0.4.0" from @***@***.*** npm WARN ***@***.***/jest-schematic npm WARN npm WARN Could not resolve dependency: npm WARN peer inquirer@"^5.0.0 || ^6.0.0" from ***@***.*** npm WARN ***@***.***/schematics-core/node_modules/inquirer-autocomplete-prompt npm WARN inquirer-autocomplete-prompt@"1.0.1" from @***@***.*** npm WARN ***@***.***/schematics-core npm WARN npm WARN Conflicting peer dependency: ***@***.*** npm WARN node_modules/inquirer npm WARN peer inquirer@"^5.0.0 || ^6.0.0" from ***@***.*** npm WARN ***@***.***/schematics-core/node_modules/inquirer-autocomplete-prompt npm WARN inquirer-autocomplete-prompt@"1.0.1" from @***@***.*** npm WARN ***@***.***/schematics-core npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: ***@***.*** npm WARN Found: ***@***.*** npm WARN node_modules/react npm WARN peerOptional react@"^16.8.0 || ^17.0.0 || ^18.0.0" from @***@***.*** npm WARN ***@***.***/addon-actions npm WARN dev @storybook/addon-actions@"^6.5.12" from the root project npm WARN 1 more ***@***.***/addon-essentials) npm WARN 94 more ***@***.***/addons, @storybook/api, ...) npm WARN npm WARN Could not resolve dependency: npm WARN peer react@"^16.8.4 || ^17.0.0" from ***@***.*** npm WARN ***@***.***/addon-actions/node_modules/react-inspector npm WARN react-inspector@"^5.1.0" from @***@***.*** npm WARN ***@***.***/addon-actions npm WARN npm WARN Conflicting peer dependency: ***@***.*** npm WARN node_modules/react npm WARN peer react@"^16.8.4 || ^17.0.0" from ***@***.*** npm WARN ***@***.***/addon-actions/node_modules/react-inspector npm WARN react-inspector@"^5.1.0" from @***@***.*** npm WARN ***@***.***/addon-actions npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: @***@***.*** npm WARN Found: ***@***.*** npm WARN node_modules/react npm WARN peerOptional react@"^16.8.0 || ^17.0.0 || ^18.0.0" from @***@***.*** npm WARN ***@***.***/addon-actions npm WARN dev @storybook/addon-actions@"^6.5.12" from the root project npm WARN 1 more ***@***.***/addon-essentials) npm WARN 94 more ***@***.***/addons, @storybook/api, ...) npm WARN npm WARN Could not resolve dependency: npm WARN peer react@"^16.13.1 || ^17.0.0" from @***@***.*** npm WARN ***@***.******@***.***/react npm WARN @mdx-js/react@"^1.6.22" from @***@***.*** npm WARN ***@***.***/addon-docs npm WARN npm WARN Conflicting peer dependency: ***@***.*** npm WARN node_modules/react npm WARN peer react@"^16.13.1 || ^17.0.0" from @***@***.*** npm WARN ***@***.******@***.***/react npm WARN @mdx-js/react@"^1.6.22" from @***@***.*** npm WARN ***@***.***/addon-docs npm WARN deprecated ***@***.***: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated ***@***.***: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies npm WARN deprecated ***@***.***: Use your platform's native performance.now() and performance.timeOrigin. npm WARN deprecated ***@***.***: See https://github.com/lydell/source-map-url#deprecated npm WARN deprecated ***@***.***: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated ***@***.***: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated ***@***.***: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated ***@***.***: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated ***@***.***: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added npm WARN deprecated ***@***.***: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. ... added 3562 packages, and audited 3763 packages in 5m 403 packages are looking for funding run `npm fund` for details 33 vulnerabilities (4 moderate, 28 high, 1 critical) npm audit fix complained about the same dependencies as install, so probably it would be best to fix those first.

…

On Sat, Jun 17, 2023 at 6:16 PM Gerome Grignon ***@***.***> wrote: Hello Christopher, for a quick fix on your side, you can run nom install with --force. On my latest dependancy update, I missed the eslint part to match angular core version. However forcing installation with a different eslint version will still work. — Reply to this email directly, view it on GitHub <#126 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGEGTUYBWFTQNP6J7WUQM23XLVDSTANCNFSM6AAAAAAZJ67WPU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Chris Tillman Developer