`npm run setup` uses dynamically linked Prisma which fails on NixOS

[aryanjassal]

Have you experienced this bug with the latest version of the template?

Yes

Steps to Reproduce

Attempt to create the project by running npx create-remix@latest --template remix-run/indie-stack and select the default values for everything. Wait, and observe the error.

Expected Behavior

The project should be initialised properly without issues.

Actual Behavior

After a while, the setup fails on the step where it is meant to run the setup script (npm run setup). In that script, the failing command is prisma migrate deploy.

$ npm run setup
> setup
> prisma generate && prisma migrate deploy && prisma db seed

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma

✔ Generated Prisma Client (v5.22.0) to ./node_modules/@prisma/client in 45ms

Start by importing your Prisma Client (See: https://pris.ly/d/importing-client)

Help us improve the Prisma ORM for everyone. Share your feedback in a short 2-min survey: https://pris.ly/orm/survey/release-5-22

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "data.db" at "file:./data.db?connection_limit=1"

Error: Could not parse schema engine response: SyntaxError: Unexpected token 'N', "NixOS cann"... is not valid JSON

I'm assuming the message is meant to be the standard Nix message for cases where a dynamically linked binary is run, "NixOS cannot run dynamically linked executables intended for generic linux environments out of the box." This is happening even though I have prisma installed on my system via home manager and have confirmed that it is available. Running prisma migrate deploy manually works, but I'm not sure if running the commands manually is enough to complete the full setup.

[aryanjassal]

The next command in the sequence, prisma db seed, also fails to run as tsx cannot be found in the runtime. To get around this, I had to modify the package.json and change the Prisma seed command from tsx prisma/seed.ts to npx tsx prisma/seed.ts, which resulted in the seed command executing.

After this, I was able to run npm install and npm run dev to see the server working in my local environment.