Skip to content
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

Unable to run npm i with npm version 8 and nodejs v16 #223

Open
Hoang-Minh opened this issue Apr 5, 2023 · 1 comment
Open

Unable to run npm i with npm version 8 and nodejs v16 #223

Hoang-Minh opened this issue Apr 5, 2023 · 1 comment

Comments

@Hoang-Minh
Copy link

Expected Behavior

Install all dependencies properly

[REQUIRED] Describe expected behavior

All the node pacakges in package.json must be installed properly

Describe the problem

Unable to run command npm i

[REQUIRED] Actual Behavior

...
1654 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\node_modules@npmcli\promise-spawn\lib\index.js:63:27)
1654 verbose stack at ChildProcess.emit (node:events:527:28)
1654 verbose stack at maybeClose (node:internal/child_process:1092:16)
1654 verbose stack at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
1655 verbose pkgid @openid/[email protected]
1656 verbose cwd C:\AppAuth-JS
1657 verbose Windows_NT 10.0.22621
1658 verbose node v16.16.0
1659 verbose npm v8.11.0
1660 error code 1
1661 error path C:\AppAuth-JS
1662 error command failed
1663 error command C:\WINDOWS\system32\cmd.exe /d /s /c npm run-script --silent build-app
1664 verbose exit 1
1665 timing npm Completed in 18065ms
1666 verbose code 1
1667 error A complete log of this run can be found in:
1667 error C:\Users\minhv\AppData\Local\npm-cache_logs\2023-04-05T12_49_22_141Z-debug-0.log

[REQUIRED] Steps to reproduce the behavior

  1. Git clone the project
  2. run npm i

[REQUIRED] Environment

  • AppAuth-JS version: latest
  • AppAuth-JS Environment (Node, Browser (UserAgent), ...): Npm version 8, Nodejs version 16
  • Source code snippts (inline or JSBin)
@node-traversal
Copy link

Is this project being maintained? Or at least open to pull requests? As mentioned the node version required for the project appears to be quite old as is the package lock and many of the dependencies have vulnerabilities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants