App Platform keeps using cached node_modules

Posted April 11, 2021 599 views
Node.jsCachingDigitalOcean App Platform

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?

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.

Submit an Answer
1 answer

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

  • … yeah, I bet you’re “working” on it.

    • Here are some troubleshooting steps I’d recommend:

      1. Review the deployment’s build logs and make sure the right Git commit is being built. The commit hash is printed at the top.
      2. Make sure the package-lock.json changed are also committed to the repo.
      3. Review the deployments tab—it’s possible that the new deployment with the new changes failed and the app was rolled back to a previous working deployment.

      If this all still seems fine, please open a support ticket and we’ll take a closer look at your app and find out why the cache isn’t being cleared as expected.