-
-
Notifications
You must be signed in to change notification settings - Fork 424
chore: cache node_modules in CI jobs #1023
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
Closed
+36
−1
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
pnpm GitHub Actions cache setup best practices node_modules💡 Result:
Best practices (pnpm + GitHub Actions caching)
node_modules.actions/setup-nodeexplicitly does not cachenode_modules; it caches package-manager data (for pnpm: the store) instead. [1]actions/setup-node) whenever possible: setcache: 'pnpm'so you don’t have to hand-rollactions/cachekeys/paths. [1][2]cache-dependency-pathto the correctpnpm-lock.yamllocation(s), otherwise the cache key may not reflect the right dependency graph. [1]packageManager(or explicit action version) to keep installs reproducible across runners/over time (e.g.,pnpm/action-setup@v4+version: 10, or rely onpackageManagerinpackage.json). [3]pnpm/action-setupcaching instead, enable its store caching (cache: true) and (for monorepos) point it at the right lockfile(s) viacache_dependency_path. [3]Recommended workflow snippet (most common / simplest)
Sources: actions/setup-node caching behavior +
cache-dependency-path+ “does not cache node_modules” [1]; pnpm’s GitHub Actions example usingcache: "pnpm"[2]; pnpm/action-setup cache inputs (cache,cache_dependency_path) [3].References
[1] https://github.com/actions/setup-node
[2] https://pnpm.io/next/continuous-integration
[3] https://github.com/pnpm/action-setup
🏁 Script executed:
Repository: npmx-dev/npmx.dev
Length of output: 43
🏁 Script executed:
Repository: npmx-dev/npmx.dev
Length of output: 1635
🏁 Script executed:
Repository: npmx-dev/npmx.dev
Length of output: 1415
Remove the manual
actions/cachestep fornode_modules.The
pnpm/action-setupwithcache: true(line 37) already caches the pnpm store, making the separatenode_modulescache (lines 39–42) redundant and potentially problematic. According to pnpm's official guidance,node_modulesshould not be cached directly because it contains symlinks to the pnpm store. Caching both separately creates a risk of broken symlinks if the cache restoration order or state becomes inconsistent.The recommended approach is to rely solely on the pnpm store cache provided by
pnpm/action-setupwithcache: true. Remove theactions/cachestep entirely.Alternatively, consider using
actions/setup-nodewithcache: 'pnpm'instead, which provides built-in, first-class support for pnpm caching and automatically includes the Node.js version in the cache key to prevent native module compatibility issues.