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

Fix for npm ci caching #1009

Merged
merged 5 commits into from
Jun 3, 2022
Merged

Fix for npm ci caching #1009

merged 5 commits into from
Jun 3, 2022

Conversation

colincasey
Copy link
Contributor

@colincasey colincasey commented Jun 2, 2022

Since npm ci removes any existing node_modules folder before installing, to get proper caching behavior we need to cache the npm cache instead.

Fixes #1006, W-11214630

Since `npm ci` removes any existing `node_modules` folder before installing, to get proper caching behavior we need to cache the npm cache instead.
@colincasey colincasey requested a review from a team as a code owner June 2, 2022 20:41
@colincasey colincasey self-assigned this Jun 2, 2022
Since `npm ci` removes any existing `node_modules` folder before installing, to get proper caching behavior we need to cache the npm cache instead.
lib/cache.sh Outdated Show resolved Hide resolved
test/run Show resolved Hide resolved
Since `npm ci` removes any existing `node_modules` folder before installing, to get proper caching behavior we need to cache the npm cache instead.
Since `npm ci` removes any existing `node_modules` folder before installing, to get proper caching behavior we need to cache the npm cache instead.
Copy link
Member

@joshwlewis joshwlewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

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

Successfully merging this pull request may close these issues.

No dependency caching when npm ci is used.
3 participants