Skip to content

fix(railway): add .npmrc with legacy-peer-deps to fix Nixpacks build conflict#331

Merged
flyblackbox merged 1 commit into
QuoteVote:mainfrom
Anton-dev3306:fix/add-npmrc-legacy-peer-deps
May 10, 2026
Merged

fix(railway): add .npmrc with legacy-peer-deps to fix Nixpacks build conflict#331
flyblackbox merged 1 commit into
QuoteVote:mainfrom
Anton-dev3306:fix/add-npmrc-legacy-peer-deps

Conversation

@Anton-dev3306
Copy link
Copy Markdown
Contributor

Description

This PR fixes the Railway build failure caused by a peer dependency conflict between [email protected] and @livechat/[email protected], which requires react@^16.3.0.

Nixpacks runs npm install during the Railway build without the --legacy-peer-deps flag, causing an ERESOLVE error. The project already uses --legacy-peer-deps in its install:all script, but Nixpacks does not pick that up automatically.

Adding a .npmrc file at the monorepo root with legacy-peer-deps=true makes the flag available at the build level regardless of which command Railway runs.

Changes

  • Added .npmrc at monorepo root: Sets legacy-peer-deps=true to resolve the Nixpacks peer dependency conflict during Railway builds.

Verification

  • This fix is consistent with Railway's own build diagnosis suggestion.
  • The existing --legacy-peer-deps flag in install:all confirms this is the intended approach for this project.

Related Issue

Related to the Railway build failures observed in #328 and previous deploys.

@netlify
Copy link
Copy Markdown

netlify Bot commented May 10, 2026

Deploy Preview for quotevote canceled.

Name Link
🔨 Latest commit 19817a5
🔍 Latest deploy log https://app.netlify.com/projects/quotevote/deploys/69ffcc8eba84080008d0444a

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.

2 participants