Unable to run npm i with npm version 8 and nodejs v16
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 165
- PR merge metrics
- No merged PRs in 30d
Description
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/appauth@1.3.1
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
- Git clone the project
- 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)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with package.json and the build-app script invoked during npm i. Reproduce the install on Windows with Node 16 and npm 8, then inspect the complete build output beyond the provided stack trace. Done means all package.json dependencies install successfully and the build-app script completes without error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100