Eric Allam
aa9f1112ea
## Summary The Prisma CLI was missing from production builds of the webapp image, so anything that shells out to `prisma` at startup failed. The container entrypoint and the standalone migration step both run `prisma migrate deploy` / `prisma migrate status`, and those broke with `Command "prisma" not found`. ## Fix `prisma` was a `devDependency` of `@trigger.dev/database`. It had only been landing in the pruned `--prod` install as a side effect of pnpm auto-installing it as a peer of `@prisma/client`. A recent dependency change shifted peer resolution so prisma stopped being materialized into the production tree, and the CLI disappeared from the image. Moving `prisma` into `dependencies` of `@trigger.dev/database` makes the CLI an explicit part of production installs. It lands in the webapp image only: the separately deployed supervisor, coordinator, and provider images don't reach the database package in their production trees (`core` only `devDepends` on it, so it isn't transitive), so they're unaffected. Verified against a locally built production image: `pnpm --filter @trigger.dev/database exec prisma --version` now resolves the CLI and the schema engine instead of failing.
28 lines
820 B
JSON
28 lines
820 B
JSON
{
|
|
"name": "@trigger.dev/database",
|
|
"private": true,
|
|
"version": "0.0.2",
|
|
"main": "./dist/index.js",
|
|
"types": "./dist/index.d.ts",
|
|
"dependencies": {
|
|
"@prisma/client": "6.14.0",
|
|
"decimal.js": "^10.6.0",
|
|
"prisma": "6.14.0"
|
|
},
|
|
"devDependencies": {
|
|
"@types/decimal.js": "^7.4.3",
|
|
"rimraf": "6.0.1"
|
|
},
|
|
"scripts": {
|
|
"clean": "rimraf dist",
|
|
"generate": "prisma generate",
|
|
"db:migrate:dev:create": "prisma migrate dev --create-only",
|
|
"db:migrate:deploy": "prisma migrate deploy",
|
|
"db:push": "prisma db push",
|
|
"db:studio": "prisma studio",
|
|
"db:reset": "prisma migrate reset",
|
|
"typecheck": "tsc --noEmit",
|
|
"build": "pnpm run clean && tsc --noEmit false --outDir dist --declaration",
|
|
"dev": "tsc --noEmit false --outDir dist --declaration --watch"
|
|
}
|
|
} |