-
Notifications
You must be signed in to change notification settings - Fork 0
build(deps): consolidate bumps from #2, #4, #5, #7, #15 against realigned main #26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| legacy-peer-deps=true | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Adding Useful? React with 👍 / 👎. |
||
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.
Setting
legacy-peer-deps=trueat the repo level disables peer dependency enforcement for all npm installs, which can mask unrelated peer incompatibilities and make dependency issues harder to detect. If this is only needed to bypass the react-day-picker/date-fns peer-range conflict, consider scoping it more narrowly (e.g., usingnpm ci --legacy-peer-depsin CI only, or resolving the mismatch by upgrading/reacting to the peer requirement) so future peer problems still surface during install.