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
Hi! It looks like you are using the classic Heroku Node.js buildpack, rather than the WIP next-gen Cloud Native Buildpack. Moving this issue to the correct repo :-)
@gtournie we don't test our buildpack with Digital Ocean + dokku so it's hard to say why your npm cache is not being restored and there are currently no issues with npm caching on Heroku.
That said, based on the configuration you've noted above, the only reason I can see for why the cache wouldn't be restored is if the cached folder was not stored during the previous build. At the end of a build is does the following output appear?
I just setup a new droplet on Digital Ocean, with the latest Ubuntu.
I just use a minimal configuration:
(Buildpack is automatically detected and installed. It installs heroku-buildpacks-nodejs by default)
Thing is, everytime I push on dokku it says:
Here's my env:
Is there something I forgot to do to activate npm's cache?
The text was updated successfully, but these errors were encountered: