Open danielleadams opened 3 years ago
This issue has been linked to a new work item: W-8711501
Maybe a good idea instead of just discarding the cache for node_modules would be just adding a --cache
option to the npm ci
call passing a directory that the buildpack could use for cache (like Gitlab CI suggests, for instance). So we could have some performance improvement by not doing unnecessary network requests while also having the speedup of the npm ci
.
I'm not totally sure if this would be good for another issue or if it could be something that could be added as an enhancement in this issue...
This issue has been linked to a new work item: W-8870770
With the current implementation of
npm ci
usage too create the build environment and Heroku slug, the buildpack will restore the cache at the beginning of the build and save the cache at the end of the build.As recommended by the npm docs (https://docs.npmjs.com/cli/v6/commands/npm-ci#description), there should be no
node_modules
before annpm ci
run because the command will delete thenode_modules
anyways. (The Heroku buildpack will pullnode_modules
from the previous build and restore them to the node_modules directory if the build is configured to useNODE_MODULES_CACHE
.)