Cannot run prisma seeds on production

[deft nacelle]

Im using regular indie stack with prisma.

If I SSH into the VPS where the remix app is deployed and try to run from the app folder the npx prisma seed command I get a error:

Running seed command `ts-node --require tsconfig-paths/register prisma/seed.ts` ...

An error occurred while running the seed command:
Error: Command failed with ENOENT: ts-node --require tsconfig-paths/register prisma/seed.ts
spawn ts-node ENOENT```

If I install ts-node there with ```npm install``` i can run aftwards the ```npx run prisma db seed` command```

Its very strange, anyone seen this issue?

BTW. I have ts-node in my package.json for both development and production dependency

[hushed crescent]

Is that hosted on fly.io? I know part of the build steps are pruning off dependencies if a fresh npm install makes it work, my guess would be that your ts-node is actually only a dev dependency. I don’t believe any package can be installed as both dev and regular dependency. So if it shows up in dev it shouldn’t exist in regular deps

[deft nacelle]

no its on a digital ocean dokku deployed vps.