94edfe08bc
Following Prisma's official documentation for deployment caching issues: https://www.prisma.io/docs/orm/more/help-and-troubleshooting/vercel-caching-issue Changes: - Add 'prisma generate' to build script (official Prisma recommendation) - Add postinstall script for automatic client generation - Remove custom stub generator workaround - Keep runtime Prisma client generation in entrypoint.sh for reliability - Add openssl to runtime container (required for Prisma engines) This follows Prisma best practices: explicitly run prisma generate during the build process to ensure Prisma Client is always up-to-date. The entrypoint script regenerates the client at runtime to guarantee engine availability in the production environment.
38 lines
1.0 KiB
JSON
38 lines
1.0 KiB
JSON
{
|
|
"name": "caddy-proxy-manager",
|
|
"version": "1.0.0",
|
|
"description": "Caddy Proxy Manager - web UI for managing Caddy reverse proxies with OAuth2 authentication.",
|
|
"private": true,
|
|
"scripts": {
|
|
"dev": "next dev",
|
|
"build": "prisma generate && next build",
|
|
"start": "next start",
|
|
"lint": "next lint",
|
|
"typecheck": "tsc --noEmit",
|
|
"postinstall": "prisma generate || echo 'Prisma generate skipped'"
|
|
},
|
|
"dependencies": {
|
|
"@emotion/react": "^11.14.0",
|
|
"@emotion/styled": "^11.14.1",
|
|
"@mui/icons-material": "^7.3.4",
|
|
"@mui/material": "^7.3.4",
|
|
"@prisma/client": "^6.18.0",
|
|
"@types/better-sqlite3": "^7.6.13",
|
|
"bcryptjs": "^3.0.2",
|
|
"better-sqlite3": "^12.4.1",
|
|
"next": "^16.0.1",
|
|
"next-auth": "^5.0.0-beta.30",
|
|
"prisma": "^6.18.0",
|
|
"react": "^19.2.0",
|
|
"react-dom": "^19.2.0"
|
|
},
|
|
"devDependencies": {
|
|
"@types/node": "^24.9.2",
|
|
"@types/react": "^19.2.2",
|
|
"@types/react-dom": "^19.2.2",
|
|
"eslint": "^9.38.0",
|
|
"eslint-config-next": "^16.0.1",
|
|
"typescript": "^5.9.3"
|
|
}
|
|
}
|