Report this

What is the reason for this report?

App Platform keeps using cached node_modules

Posted on April 11, 2021

Looks like node_modules is getting cached really hard. I’ve made big changes to my package.json and package-lock.json and they don’t reflect in my build.

For instance I changed the version of my package.json from 2.0.0 to 2.1.5 and when it builds, it’s still using 2.0.0 as well as the deps of the older package.json file.

Is there a way to manually clear the Apps node_modules cache?



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

👋🏼 @camdagr8

App Platform reuses cached node_modules if the contents of package-lock.json or yarn.lock match the cached version.

Unfortunately there isn’t a way to clear the cache (we’re working on it!), but if this is still not working for you, one workaround would be to rename the component which will assign it a new empty cache.

Solved by adding app level enviroment variable NODE_MODULES_CACHE=false.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.