Skip to content

Commit

Permalink
build(api): set production NODE_ENV when migrating in prod
Browse files Browse the repository at this point in the history
Previously, migrating failed because `NODE_ENV` wasn't set and `pino`
tried to use `pino-pretty` for formatting the output.

Related to #83
  • Loading branch information
JoosepAlviste committed Jan 6, 2024
1 parent 0e189a1 commit 44d8773
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion apps/api/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@
"lint": "eslint src && madge --circular --extensions ts ./src",
"lint:fix": "eslint --fix src",
"migrate": "tsx bin/migrate.ts && pnpm codegen:db",
"migrate:prod": "dotenv -e ../../.env node dist/bin/migrate.js",
"migrate:prod": "NODE_ENV=production dotenv -e ../../.env node dist/bin/migrate.js",
"migrate:test": "dotenv -e ../../.env.test tsx bin/migrate.ts",
"migration": "./bin/createMigration.sh",
"start": "NODE_ENV=development tsx watch --clear-screen=false src/main.ts",
Expand Down

0 comments on commit 44d8773

Please sign in to comment.