You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 5, 2020. It is now read-only.
In Rocketeer 2 there is no special mechanism in place for this (there is in Rocketeer 3 but it is not out yet). You however have several solutions at hand:
Place node_modules in your shared folders so that it is reused between releases. This however makes rollbacks more difficult so it is to keep in mind
Copy the node_modules from the previous release in a before hook, if it exists
Finally before doing this you can solve the issue at the package manager level – ie. look into why it is taking several minutes in the first place. Maybe give a shot at either Yarn or NPM5 which both provide faster installation times for Node dependencies. There are also some wrappers around NPM like npm-cache and stuff, older versions of NPM were notably slow so you should find things pretty easily on the web
I'd recommend to do this first because even if you can make it fast for deployments you're really just working around the problem and it will still be slow for you locally and for every first deployment on a new server, and so on.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there a way to cache the
node_modules
folder? It's taking several minutes to install all the node packages on each deploy.The text was updated successfully, but these errors were encountered: