Files
TicketingSystem/server/package.json
josh 429a530fc8
All checks were successful
Build & Push / Build Server (push) Successful in 1m35s
Build & Push / Build Client (push) Successful in 40s
Use prisma db push instead of migrate deploy on startup
Eliminates the need to generate and commit migration files locally
before first deploy. Schema is synced directly from schema.prisma
on container start.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-30 19:59:55 -04:00

37 lines
947 B
JSON

{
"name": "ticketing-server",
"version": "1.0.0",
"scripts": {
"dev": "tsx watch src/index.ts",
"build": "tsc",
"start": "node dist/index.js",
"start:prod": "prisma db push && node dist/index.js",
"db:migrate": "prisma migrate dev",
"db:push": "prisma db push",
"db:generate": "prisma generate",
"db:seed": "tsx prisma/seed.ts"
},
"dependencies": {
"@prisma/client": "^5.22.0",
"bcryptjs": "^2.4.3",
"cors": "^2.8.5",
"dotenv": "^16.4.7",
"express": "^4.21.2",
"express-async-errors": "^3.1.0",
"jsonwebtoken": "^9.0.2",
"node-cron": "^3.0.3",
"zod": "^3.23.8"
},
"devDependencies": {
"@types/bcryptjs": "^2.4.6",
"@types/cors": "^2.8.17",
"@types/express": "^4.17.21",
"@types/jsonwebtoken": "^9.0.7",
"@types/node": "^22.10.0",
"@types/node-cron": "^3.0.11",
"prisma": "^5.22.0",
"tsx": "^4.19.2",
"typescript": "^5.7.2"
}
}