Fix:Either set the Root Directory to where your actual app lives (e.g. workspace/api-server). (Service Settings > Root Directory)Or add a root package.json if this is a monorepo.{ "name": "root", "private": true, "workspaces": [ "workspace/*" ]}

i already have package.json since its monorepo but i also have railpack.json and railway.json

railpack.json{"$schema": "https://schema.railpack.com","provider": "node","packages": {"node": "20","pnpm": "9.15.9"},"env": {"NODE_ENV": "development","CI": "true","NPM_CONFIG_PRODUCTION": "false"},"steps": {"install": {"commands": ["pnpm install --no-frozen-lockfile --prod=false"]},"build": {"inputs": [{ "step": "install" }],"commands": ["pnpm --filter @workspace/api-server run build:prod"]}},"deploy": {"startCommand": "node --enable-source-maps artifacts/api-server/dist/index.mjs"}}railway.json{"$schema": "https://railway.app/railway.schema.json","build": {"builder": "RAILPACK"},"deploy": {"startCommand": "node --enable-source-maps artifacts/api-server/dist/index.mjs","healthcheckPath": "/api/healthz","healthcheckTimeout": 300,"restartPolicyType": "ON_FAILURE","numReplicas": 1}}package.json{"name": "workspace","packageManager": "pnpm@9.15.9","engines": {"node": "20"},"version": "0.0.0","license": "MIT","scripts": {"db:push": "pnpm --filter @workspace/db run push","build": "pnpm --filter @workspace/api-server run build:prod","build:all": "pnpm -r run build","typecheck:libs": "tsc --build","typecheck": "echo 'typecheck skipped (production build uses esbuild)'"},"pnpm": {"frozen-lockfile": false},"private": true,"devDependencies": {"prettier": "^3.8.1","tsx": "catalog:","typescript": "~5.9.2"},"dependencies": {"sharp": "^0.34.5"}}package.json is outside all the folder not inside anything

Even if railway.json doesn’t specify it, Railway UI might have Root Directory set.Check in Railway dashboard:Service → Settings → Root DirectoryIf it’s anything other than empty or . → that’s the issuePro tip: Try to provide the file structure in file tree mode in the future - it is much easier to read

well the root is empty so i doubt its the issuemonorepo/ ├── artifacts/ │ ├── api-server/ Express 5 API — all business logic and integrations │ ├── digor-crm/ React + Vite CRM portal (/crm/) │ ├── digor-tools/ React + Vite internal tools (/tools/) │ └── digor-website/ React + Vite public marketing site (/) ├── lib/ │ ├── api-spec/ OpenAPI 3.1 spec + Orval codegen config │ ├── api-client-react/ Generated React Query hooks │ ├── api-zod/ Generated Zod schemas │ └── db/ Drizzle ORM schema + PostgreSQL connection └── scripts/ One-off utility scripts (seeding, migrations)artifacts/api-server/src/ ├── routes/ │ ├── crm/ │ │ ├── leads.ts # Core deal routes + all AI endpoints │ │ ├── comps.ts # Comparable sales CRUD + adjustment math │ │ ├── sequences.ts # Email sequence management │ │ ├── auth.ts # JWT login/session │ │ └── ... # campaigns, users, tasks, links, stats, buyers │ ├── tools.ts # Tools portal: skip trace, distressed, ARV, lookup │ ├── signalwire.ts # SignalWire webhook + message retrieval │ ├── openphone.ts # OpenPhone webhook + message retrieval │ └── stripe.ts # Stripe checkout + webhook ├── services/ │ ├── attomApi.ts # ATTOM client with key rotation + fetchAttomAvm │ ├── propertyApi.ts # Adjustment math + AI price-per-sqft fallback │ └── emailService.ts # Nodemailer SMTP wrapper └── lib/ └── logger.ts # Pino structured logging

Root being empty in UI doesn’t guarantee it’s actually empty at build time.Add a quick debug step to print what actually exists in /app during build.Update your railpack.json install step:"install": { "commands": [ "echo ROOT CHECK", "pwd", "ls -la", "echo PACKAGE CHECK", "cat package.json || echo 'no package.json'", "pnpm install --no-frozen-lockfile --prod=false" ] }Then redeploy and check logs.What you’re looking forIf you see:no package.json in ls -laor cat package.json fails→ Railway is building the wrong directory.If you do see it:then the issue is workspace resolution (pnpm config), not root pathThis is the fastest way to remove guesswork and see exactly what Railpack mounted into /app.

Your debug step didn’t run, which is important.The log still shows only:pnpm install --no-frozen-lockfile --prod=false ERR_PNPM_NO_PKG_MANIFEST No package.json found in /appThat means one of two things:1) Your railpack.json is not being usedRailway might be ignoring it and using default build behavior.2) Different service / wrong repo pathThe service might not be building the repo root you think it is.Verify this directlyAdd something impossible to miss:"install": { "commands": [ "echo 'HELLO FROM RAILPACK'", "exit 1" ] }Redeploy.Result:If you don’t see HELLO FROM RAILPACK → your railpack.json is ignoredIf you do see it → then path/debug continues

Your debug step didn’t run, which is important.The log still shows only:pnpm install --no-frozen-lockfile --prod=false ERR_PNPM_NO_PKG_MANIFEST No package.json found in /appThat means one of two things:1) Your railpack.json is not being usedRailway might be ignoring it and using default build behavior.2) Different service / wrong repo pathThe service might not be building the repo root you think it is.Verify this directlyAdd something impossible to miss:"install": { "commands": [ "echo 'HELLO FROM RAILPACK'", "exit 1" ] }Redeploy.Result:If you don’t see HELLO FROM RAILPACK → your railpack.json is ignoredIf you do see it → then path/debug continues

Ok, so Railpack is actually working. That means the issue is the build context.Right now /app inside the container doesn’t contain your root package.json, even though it exists in your repo.Most likely causes:Root Directory is set in Railway UI (even if you didn’t set it in railway.json).railwayignore or .gitignore is excluding filesService is pointing to a subfolderNext step: replace install with this to inspect /app:"commands": [ "pwd", "ls -la", "find . -maxdepth 2 -name package.json" ]This will show exactly what Railway actually copied into the container.

actually i fixed it by using this code and it worked , thanks for helping with the Troubleshooting{"$schema": "https://railpack.com","provider": "node","packages": {"node": "20","pnpm": "9.15.9"},"variables": {"NPM_CONFIG_PRODUCTION": "false"},"deploy": {"startCommand": "node --enable-source-maps artifacts/api-server/dist/index.mjs"}}

actually i fixed it by using this code and it worked , thanks for helping with the Troubleshooting{"$schema": "https://railpack.com","provider": "node","packages": {"node": "20","pnpm": "9.15.9"},"variables": {"NPM_CONFIG_PRODUCTION": "false"},"deploy": {"startCommand": "node --enable-source-maps artifacts/api-server/dist/index.mjs"}}

Please mark the answer that helped you as accepted so the bounty can be processed <3