App Platform keeps using cached node_modules

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?

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

👋🏼 @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.