Railway Deployment #cd2cc9 fix: add packages field to workspace - #62
Merged
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
1 participant
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
The pnpm install step fails with "ERROR packages field missing or empty" because
pnpm-workspace.yamlexists but lacks the requiredpackagesfield. pnpm requires a non-emptypackagesfield whenever a workspace config file is present, even for single-package repos.Solution
Added
packages: ['.']topnpm-workspace.yamlso pnpm recognises the root directory as the sole workspace member. This satisfies pnpm's validation while preserving the existingallowBuildsconfiguration introduced in PR #61.Changes
pnpm-workspace.yamlContext
12e5b31Generated by Railway