Find a way to cache the `npm install` step during `nox -s dev`
See original GitHub issueIs your feature request related to a specific problem?
nox -s dev
takes a really long time…this appears to be primarily due to the fact that npm install
step isn’t getting cached as node_modules/
is included in the .dockerignore
file
Describe the solution you’d like
For the sake of development, we should find a way to cache or use locally installed npm modules to majorly cut down on the time needed to spin up nox -s dev
Describe alternatives you’ve considered, if any
Not sure what other options might exist yet
Additional context
N/A
Issue Analytics
- State:
- Created a year ago
- Comments:16 (16 by maintainers)
Top Results From Across the Web
Is there a way to speedup npm ci using cache? - Stack Overflow
NPM cache is located in ~/.npm but in most CIs you can only cache things inside your working directory. What you can do...
Read more >Is there a way to change the npm cache location using node ...
We are using Npm@1 in our pipelines with different versions on npm installed through UseNode@1. This is using the %AppData%/Roaming for the caching....
Read more >A Beginner's Guide to NPM - Bits and Pieces
cache : Although not normally used by developers, this command allows them to either clear, verify or add something to NPM's cache. In...
Read more >npm-cache
This command is primarily intended to be used internally by npm, but it can provide a way to add data to the local...
Read more >[BUG] `npm install` started to hang on "still idealTree ... - GitHub
Is there an existing issue for this? I have searched the existing issues See #1991 (comment) Current Behavior npm install in a fresh...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@allisonking I’m going to defer on this one until you finish up the frontend packaging PR since I don’t want to potentially create conflicts
1.8s doesn’t seem like enough time to actually install all of those modules? there’s some kind of black magic cache going on or something 😂 i don’t know how else that can be possible