Add railpack.toml to disable frozen-lockfile - #3
Open
railway-app[bot] wants to merge 1 commit into
Open
Conversation
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.
Problem
Railway's build fails with
ERR_PNPM_OUTDATED_LOCKFILEbecause Railpack runspnpm install --frozen-lockfileby default, and the build environment detects the lockfile as outdated — specifically missingnode-macaddress@^2.1.1frompackages/@hmrc-sync/collector/package.json.Solution
Added a
railpack.tomlat the repository root withfrozen_lockfile = falseunder the[install]section. This tells Railpack to omit the--frozen-lockfileflag, allowing pnpm to regenerate the lockfile during the build if there are any dependency mismatches.Changes
railpack.tomlGenerated by Railway