chore(deps): update dependency @welldone-software/why-did-you-render to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@welldone-software/why-did-you-render	8.0.3 -> 10.0.1

---

Release Notes

welldone-software/why-did-you-render (@​welldone-software/why-did-you-render)

v10.0.1

Compare Source

• notifier was not exposing ownerDataMap despite the documentation saying it should.

v10.0.0: Why Did You Render v10 Supporting React 19! 🎉🍾

Compare Source

¯\(ツ)/¯ The version was bumped from v8 to v10 directly and 10.0.0 is actually the same as the next 10.0.1. Sorry, I had some npm publishing issues ¯\(ツ)/¯

[!NOTE]
I've joined the React team, specifically working on React tooling. This role has opened up exciting opportunities to enhance the developer experience for React users— and your input could offer valuable insights to help me with this effort. Please join the conversation in the discussion thread!

Breaking Changes

• welldone-software/why-did-you-render@45fcdcf, welldone-software/why-did-you-render@7b6fc5c, welldone-software/why-did-you-render@0b3cdd9, welldone-software/why-did-you-render@7eed9c5 - Now supports React 19 🎉🍾
  • Older versions are not supported, however I've created version branches with specific readme for older versions and added that information to the main readme:
    • version 8 of the library that supports React 18
    • and version 7 of the library for React 17 and React 16
• welldone-software/why-did-you-render@0613270 - Advanced settings and exposed internals changes:
  • Custom notifier callback props were renamed from prevHook and nextHook to prevHookResult and nextHookResult
  • For advanced use-cases- wdyrStore.hooksPerRender was renamed to wdyrStore.hooksInfoForCurrentRender

[!CAUTION]
The library was not tested with React Compiler at all. I believe it's completely incompatible with it.

[!CAUTION]
Not all re-renders are "bad". Sometimes shenanigan to reduce re-renders can either hurt your App's performance or have a neglagable effect, in which case it would be just a waste of your efforts, and complicate your code. Try to focus on heavier components when optimizing and use the React DevTools Profiler to measure the effects of any changes.

New Features

• welldone-software/why-did-you-render@1562bfc - Improved console colors so the text is now clearly visible in dark mode. This can be adjusted via the setting textBackgroundColor.

Internal

• welldone-software/why-did-you-render@cdd84dc, welldone-software/why-did-you-render@2eb3f93, welldone-software/why-did-you-render@6c617d6 - Re-worked how owner render reasons are detected
• welldone-software/why-did-you-render@6bd8f0c - Fixed how the demo app is being ran and using fast-refresh instead of the old hot-reload
• welldone-software/why-did-you-render@0613270 - Made the detection of hooks in a new component much more simple, clear, and accurate
• welldone-software/why-did-you-render@8cb3d36, welldone-software/why-did-you-render@5e927f2 - Adjusted tests to React 19
• welldone-software/why-did-you-render@cd969a0 - Only testing the latest libraries that are compatible with React 19.
• welldone-software/why-did-you-render@7eed9c5 - Eliminated a warning that forwardRef functions accept exactly two parameters. Added a demo page for forwardRef.
• welldone-software/why-did-you-render@db2914c - Updated eslint to version 9
• welldone-software/why-did-you-render@3fb801c - Removed all dev packages that were not used
• welldone-software/why-did-you-render@fcc8a8f, welldone-software/why-did-you-render@1f524c0 - Updated the rest of the dev packages, and adjusted the code accordingly

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"18.3.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^19" from @welldone-software/[email protected]
npm error node_modules/@welldone-software/why-did-you-render
npm error   dev @welldone-software/why-did-you-render@"10.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-01-23T07_50_13_986Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-23T07_50_13_986Z-debug-0.log

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
moviesmap	❌ Failed (Inspect)			Jan 23, 2025 7:51am