How do I disable caching for node_modules in the App Platform build?
Prisma relies on code generation during the build process to function properly. The code is generated into the
If you look at the error that the user encountered, it appears that the reason might be the way that you cache the
node_modules folder. It seems that changes to the
package-lock.json file clears the cache.
Is there a way to either disable the caching or provide a workaround so that code generated into the
node_modules folder during the build will be included in the release?
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.×