I'm deploying a Node.js monorepo using Yarn workspaces on Railway, but I'm facing persistent module resolution issues despite trying multiple approaches.

The error:

Error: Cannot find module '/app/packages/server/api/node_modules/@wavenotes-new/shared/dist/index.js'. Please verify that the package.json has a valid "main" entry
  code: 'MODULE_NOT_FOUND',
  path: '/app/packages/server/api/node_modules/@wavenotes-new/shared/package.json',
  requestPath: '@wavenotes-new/shared'

My setup:

Monorepo with Yarn 4 workspaces

.railway.toml configuration

Custom nixpacks.toml configuration

Services: API and Worker

What I've tried:

• Explicitly copying the shared package to node_modules during build
• Setting the correct main entry in package.json
• Creating global node_modules links
• Setting NODE_PATH environment variable
• Different copying approaches (cp -r vs cp -rf)
• Verifying the dist files exist in various locations
• Adding verification steps in the build process
• Despite all these approaches and verification steps showing that the files exist in the correct locations during build time, at runtime Node.js still can't find the module.

My specific questions:

• What's the recommended approach for handling internal workspace packages in Railway deployments?
• Is there a configuration setting I'm missing for monorepo deployments?
• Could there be something happening between the build and runtime phases that's affecting module resolution?
• Are there specific debug logs/commands I can use to better diagnose this issue?

Any insights would be greatly appreciated, as I've spent significant time trying to resolve this.

View Deploy details

ⓘ Deployment information is only viewable by project members and Railway employees.