Fix seed.ts module resolution: move to backend/prisma/
ts-node resolved node_modules relative to the script path, so running from prisma/seed.ts (outside backend/) never found bcryptjs or @prisma/client in backend/node_modules — the seed silently failed on every container start. Moving the script under backend/prisma/ fixes resolution; also adds a missing .gitignore for node_modules.
This commit is contained in:
parent
c8a5984f8b
commit
d1b2447d92
4
.gitignore
vendored
Normal file
4
.gitignore
vendored
Normal file
@ -0,0 +1,4 @@
|
||||
node_modules/
|
||||
dist/
|
||||
.env
|
||||
*.log
|
||||
1997
backend/package-lock.json
generated
Normal file
1997
backend/package-lock.json
generated
Normal file
File diff suppressed because it is too large
Load Diff
@ -3,7 +3,7 @@
|
||||
"version": "1.0.0",
|
||||
"private": true,
|
||||
"prisma": {
|
||||
"seed": "ts-node ../prisma/seed.ts"
|
||||
"seed": "ts-node prisma/seed.ts"
|
||||
},
|
||||
"scripts": {
|
||||
"dev": "ts-node-dev --respawn -r dotenv/config src/app.ts",
|
||||
|
||||
Loading…
Reference in New Issue
Block a user