Files
npm-statuspage/package.json
Fredrik Johansson edfa12b8e9
All checks were successful
Docker / build-and-push (push) Successful in 2m8s
Fix: .env was never actually loaded for local dev
README said cp .env.example .env then npm run dev, but nothing ever
read the file into process.env — no dotenv, no --env-file. This
predates the admin UI work; just surfaced by actually trying to run
it. Fixed with Node's native --env-file flag on both dev and start
(no new dependency). Doesn't affect Docker, which gets its config
from docker-compose's environment: block directly, bypassing npm
scripts entirely (CMD calls node dist/index.js directly).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-10 15:49:56 +02:00

23 lines
492 B
JSON

{
"name": "status",
"version": "0.1.0",
"license": "MIT",
"type": "module",
"scripts": {
"dev": "tsx watch --env-file=.env src/index.ts",
"build": "tsc",
"start": "node --env-file=.env dist/index.js"
},
"dependencies": {
"express": "^4.19.2",
"better-sqlite3": "^11.3.0"
},
"devDependencies": {
"@types/express": "^4.17.21",
"@types/node": "^22.0.0",
"@types/better-sqlite3": "^7.6.11",
"tsx": "^4.15.0",
"typescript": "^5.5.0"
}
}