chore(deps): widen react-day-picker peer range to v10 - #2
Merged
Conversation
The component code is compatible with the v10 API; existing v9 consumers remain supported via the OR range.
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
Allow react-day-picker v10 alongside v9 in peerDependencies.
Why
v0.2.0 published with
react-day-picker: ^9.4.3only. Host apps on v10 (current stable) hit ERESOLVE onnpm install monorailphp@^0.2.0. The v10 API surface used bycalendar.tsx(DayPicker,classNames,month_caption,caption_label) is compatible.Test plan