Fix npm install in debug Dockerfile with legacy-peer-deps flag#68
Merged
Conversation
Adds --legacy-peer-deps flag to npm install command in the debug Dockerfile to resolve peer dependency conflicts during Docker build. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
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.
Summary
--legacy-peer-depsflag tonpm installcommand in server/Dockerfile.debugProblem
The debug Dockerfile was failing during
npm installdue to peer dependency conflicts between packages.Solution
Added the
--legacy-peer-depsflag to bypass strict peer dependency resolution, allowing the build to complete successfully while maintaining backward compatibility.Test plan
npm run docker:build:debugnpm run docker:up:debug🤖 Generated with Claude Code