Repository navigation
Fix the API image build when apps/api has no nested deps - #8
Merged
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
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.
The dotenv bump in #4 let npm hoist the last dependency that was installed under
apps/api/node_modules, so that directory is no longer created and the runtime stage'sCOPY --from=builder /repo/apps/api/node_modulesfails. docker-publish has failed on master since #4.The builder stage now creates the directory after the production prune, so the copy works whether or not npm nests anything there.
Verified locally: the API image builds, and
dotenvand@nestjs/coreload in it on Node 24.22.1.