Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .npmrc
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
legacy-peer-deps=true

Copilot AI Apr 27, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Setting legacy-peer-deps=true at 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., using npm ci --legacy-peer-deps in CI only, or resolving the mismatch by upgrading/reacting to the peer requirement) so future peer problems still surface during install.

Suggested change
legacy-peer-deps=true

Copilot uses AI. Check for mistakes.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Avoid disabling peer dependency checks globally

Adding .npmrc with legacy-peer-deps=true suppresses peer-dependency validation for all installs, which masks real incompatibilities introduced here (for example, react-day-picker@8.10.1 peers on date-fns ^2 || ^3 while package.json now pins date-fns ^4.1.0, visible in package-lock.json line 11992). Keeping this override repo-wide shifts dependency breakage from install-time into harder-to-debug runtime/test behavior.

Useful? React with 👍 / 👎.

Loading
Loading