After deploying my app that uses some generators at the dependency install step (scripts | npm Docs) in this case, https://prisma.io which generates my database client.
as I pushed several migrations to my repo and had them deploy on Qovery, despite running this generator step before every start command:
"start": "prisma generate && ts-node src/index.ts",
The app is using a buildpack.
The original client that was generated many revisions ago never gets overwritten.
Ideally, I would like to be able to clear the cache on every deploy.
After changing the build step of my
package.json the new command was run on deploy, but afterwards, throws an error mentioning my old build command:
27 Sep, 00:26:53.679 > start 27 Sep, 00:26:53.679 > node dist/index.js 27 Sep, 00:26:53.679 27 Sep, 00:26:55.176 🚀 Server ready 27 Sep, 00:26:56.106 🔐 MetadataService initialized 27 Sep, 00:27:29.827 npm notice 27 Sep, 00:27:29.827 npm notice New patch version of npm available! 7.24.0 -> 7.24.1 27 Sep, 00:27:29.827 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v7.24.1> 27 Sep, 00:27:29.827 npm notice Run `npm install -g firstname.lastname@example.org` to update! 27 Sep, 00:27:29.827 npm notice 27 Sep, 00:27:29.829 npm ERR! path /workspace 27 Sep, 00:27:29.831 npm ERR! command failed 27 Sep, 00:27:29.831 npm ERR! signal SIGTERM 27 Sep, 00:27:29.831 npm ERR! command sh -c prisma generate && ts-node src/index.ts 27 Sep, 00:27:29.840 27 Sep, 00:27:29.840 npm ERR! A complete log of this run can be found in: 27 Sep, 00:27:29.840 npm ERR! /app/.npm/_logs/2021-09-26T14_27_29_832Z-debug.log