Repository navigation
[EngSys] Use actions/cache for "npm ci" to improve perf #32896
Description
https://github.com/actions/cache/blob/main/examples.md#node---npm
On Linux, only improved perf of "npm ci" in repo root from 12s to 11s (including cache restore time), so not worth it for perf alone.
However, the cache may be more reliable, and prevent failures like this E429:
npm ci
npm error code E429
npm error 429 Too Many Requests - GET https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-08-26T07_10_24_348Z-debug-0.log
Error: Process completed with exit code 1.
Root cause of 429 was an npmjs incident, so maybe this is expected to be rare?
https://status.npmjs.org/incidents/njwnds2vmdhz
Simplest option might be to use the caching feature builtin to setup-node:
https://github.com/actions/setup-node?tab=readme-ov-file#caching-global-packages-data
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
- Status
Activity
mikeharder commentedon Feb 28, 2025
Only improved perf of "npm ci" in repo root from 12s to 11s (including cache restore time), so currently not worth the added complexity.
timotheeguerin commentedon Sep 22, 2026
Closing as completed for the current dependency-installation tooling.
#43922 migrated installation to pnpm and provides explicit actions/cache caching of the pnpm store in the shared setup-node-install-deps action. The cache is namespaced by OS, architecture, install profile, and lockfile, with restore keys and an opt-out for small installs. This supplies the requested dependency caching for the package manager now used by the repository.