npm install operations take 10+ minutes longer
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description:
- A-Frame Version: 1.3.0, 1.2.0
- Node: v14.19.3 (npm v6.14.17)
- Ubuntu 20.04.4
- Reproducible Code Snippet or URL:
npm init
npm install aframe --save
It now takes 800+ seconds for npm ci to complete, whereas a build that ran May 13th took ~60 seconds to complete. That is in an existing project but the issue is seen in fresh projects where aframe is the only dependency as shown above. If aframe is removed as a dependency then the time to run npm ci returns to around 40-60 seconds.
I am seeing this across multiple machines as well as when setting up a fresh docker container with node:14, creating an npm project and installing aframe there.
The installation seems to hang a long time on fetchMetadata: resolveWithNewModule aframe@1.3.0 checking installable status
Are there any ideas on why this might have started happening suddenly?
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
Reproduce the report with npm init, npm install aframe --save, and npm ci using Node 14, including the node:14 container mentioned. Start by inspecting the npm timing output around fetchMetadata and comparing installs with and without A-Frame. Done means identifying the cause of the regression and confirming that a fresh A-Frame install no longer incurs the reported delay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100