fix(railway): add .npmrc with legacy-peer-deps to fix Nixpacks build conflict#331
Merged
flyblackbox merged 1 commit intoMay 10, 2026
Conversation
✅ Deploy Preview for quotevote canceled.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes the Railway build failure caused by a peer dependency conflict between
[email protected]and@livechat/[email protected], which requiresreact@^16.3.0.Nixpacks runs
npm installduring the Railway build without the--legacy-peer-depsflag, causing anERESOLVEerror. The project already uses--legacy-peer-depsin itsinstall:allscript, but Nixpacks does not pick that up automatically.Adding a
.npmrcfile at the monorepo root withlegacy-peer-deps=truemakes the flag available at the build level regardless of which command Railway runs.Changes
.npmrcat monorepo root: Setslegacy-peer-deps=trueto resolve the Nixpacks peer dependency conflict during Railway builds.Verification
--legacy-peer-depsflag ininstall:allconfirms this is the intended approach for this project.Related Issue
Related to the Railway build failures observed in #328 and previous deploys.