Skip to content

fix(backend): handling prisma issues while starting the backend#8

Draft
Sanix-Darker wants to merge 1 commit intomasterfrom
fix/backend-prisma
Draft

fix(backend): handling prisma issues while starting the backend#8
Sanix-Darker wants to merge 1 commit intomasterfrom
fix/backend-prisma

Conversation

@Sanix-Darker
Copy link
Copy Markdown
Member

WHAT

  • removed multi stage from Dockerfile
  • upgraded prisma and prisma/client
  • updated the docker-compose global file

WHAT's LEFT

On yarn run am still getting :

$ node src/index.js
node:internal/modules/cjs/loader:1413
  throw err;
  ^

Error: Cannot find module '/home/dk/github/camerapps/backend/src/index.js'
    at Function._resolveFilename (node:internal/modules/cjs/loader:1410:15)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1061:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1066:22)
    at Function._load (node:internal/modules/cjs/loader:1215:37)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:234:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:151:5)
    at node:internal/main/run_main_module:33:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v23.5.0
error Command failed with exit code 1.

@Sanix-Darker Sanix-Darker self-assigned this May 9, 2025
- "${API_VOLUME_PATH:-~/camerapps}/api/public:/app/public"
ports:
- "8100:8100"
environment:
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NOTE: normally i think we should relay on the same .env file used by prisma on generate... so having environment here seems not a good idea for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant