Use CI cache to speed up `npm ci`

Open
#91 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, node.js
Domain
ci-cd

Research direction

Locate the CI workflow files that use actions/setup-node and npm ci. Add the requested npm cache configuration and prefer-offline option to the relevant workflow steps, then run the affected CI workflow to confirm dependency installation still succeeds and caching is enabled.

Written by the indexing model from the issue text.

Description

This issue is to track using of CI caches to speed up CI workflows.

To enable caching for NPM-based projects:

  • Add the cache: npm input to instances of the actions/setup-node Github Action: 
    using: actions/setup-node@v4.0.0
with:
  cache: npm
  • Add --prefer-offline to instances of npm ci
    This will stop NPM from performing "staleness" checks, without the "hard failure" of --offline.

Restrictions

The storage of cache is 10 GB per-repository, with a maximum "no access" duration of 7 days. If any of these limits are hit, they will be automatically evicted. Hence, there should not be much additional maintenance oerhead for us.

Dominant language
Shell
Stars
0
Forks
0
Avg merge
1d 3h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from loopbackio/cicd

All issues in loopbackio/cicd

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.