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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This correctly fixes the build failure. However, this pattern of manually adding a
COPYline for each new library is error-prone, as this PR itself demonstrates.A more maintainable approach would be to use a single command to copy all library
package.jsonfiles. If you are using Docker BuildKit, you can replace the entire block ofCOPYinstructions (lines 24-31) with a single line. This would automatically handle new libraries in the future.First, ensure BuildKit is enabled by adding
# syntax=docker/dockerfile:1to the top of yourDockerfile. Then, you can use:COPY --parents libs/*/package*.json ./If you can't use BuildKit, consider at least sorting the block of
COPYcommands alphabetically to make it easier to manage.