Skip to content

Railway Deployment #a6a158 fix: force Node.js provider#3

Open
railway-app[bot] wants to merge 1 commit into
mainfrom
railway/fix-deploy-a6a158
Open

Railway Deployment #a6a158 fix: force Node.js provider#3
railway-app[bot] wants to merge 1 commit into
mainfrom
railway/fix-deploy-a6a158

Conversation

@railway-app

@railway-app railway-app Bot commented Jun 4, 2026

Copy link
Copy Markdown

Problem

Railpack detected only Rust from the root Cargo.toml and did not install Node.js or pnpm, causing the build to fail with pnpm: not found (exit 127). Additionally, apps/frontend had no package.json, making it an invalid pnpm workspace member.

Solution

Added railpack.json at the repo root with "provider": "node" to force Railpack to use the Node.js provider instead of auto-detecting Rust. Added apps/frontend/package.json as @xartists/frontend with the Vite dev/build scripts and all required dependencies so the frontend is a valid pnpm workspace package.

Changes

  • Created railpack.json
  • Created apps/frontend/package.json

Context

  • Deployment: #a6a158
  • Failed commit: fda57e1

Generated by Railway

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.

0 participants