Persist npm's cache between builds #86
Closed
Conversation
This file contains 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
Allows other buildpacks to effectively make use of the cache.
|
Sweet. Can you sync with heroku master add a test case? See https://github.com/heroku/heroku-buildpack-nodejs#testing |
|
I'm closing this because it looks stale - please ping me if you'd like to reopen it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
$npm_config_cacheallows npm's cache to be location somewhere other than$HOME/.npmThis also changes cache operations to explicitly deal with
$cache_dir/node_modulesto allow composed buildpacks to effectively use the cache (otherwise the "Caching node_modules" step would stomp on other users of the cache).