Update react dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/react-dom (source)	18.2.1 -> 18.2.3
eslint-plugin-react-refresh	0.3.5 -> 0.4.1
react-router-dom	6.10.0 -> 6.11.1

---

Release Notes

ArnaudBarre/eslint-plugin-react-refresh

v0.4.1

Compare Source

• Ignore export type * (fixes #​12)
• Support for all-uppercase function wrapped in forwardRef/memo (#​11)

v0.4.0

Compare Source

Add allowConstantExport option (fixes #​8)

This option allow to don't warn when a constant (string, number, boolean, templateLiteral) is exported aside one or more components.

This should be enabled if the fast refresh implementation correctly handles this case (HMR when the constant doesn't change, propagate update to importers when the constant changes). Vite supports it, PR welcome if you notice other integrations works well.

Allow all-uppercase function exports (fixes #​11)

This only works when using direct export. So this pattern doesn't warn anymore:

export const CMS = () => <></>;

But this one will still warn:

const CMS = () => <></>;
export default CMS;

remix-run/react-router

v6.11.1

Compare Source

Patch Changes

• Updated dependencies:
  • [email protected]
  • @remix-run/[email protected]

v6.11.0

Compare Source

Minor Changes

• Enable basename support in useFetcher (#​10336)
  • If you were previously working around this issue by manually prepending the basename then you will need to remove the manually prepended basename from your fetcher calls (fetcher.load('/basename/route') -> fetcher.load('/route'))

Patch Changes

• Fix inadvertent re-renders when using Component instead of element on a route definition (#​10287)
• Fail gracefully on <Link to="//"> and other invalid URL values (#​10367)
• Switched from useSyncExternalStore to useState for internal @remix-run/router router state syncing in <RouterProvider>. We found some subtle bugs where router state updates got propagated before other normal useState updates, which could lead to footguns in useEffect calls. (#​10377, #​10409)
• Add static prop to StaticRouterProvider's internal Router component (#​10401)
• When using a RouterProvider, useNavigate/useSubmit/fetcher.submit are now stable across location changes, since we can handle relative routing via the @remix-run/router instance and get rid of our dependence on useLocation(). When using BrowserRouter, these hooks remain unstable across location changes because they still rely on useLocation(). (#​10336)
• Updated dependencies:
  • [email protected]
  • @remix-run/[email protected]

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ EDITORCONFIG	editorconfig-checker	3		0	0.01s
✅ JSON	eslint-plugin-jsonc	1	0	0	0.85s
✅ JSON	jsonlint	1		0	0.16s
✅ JSON	npm-package-json-lint	yes		no	0.48s
✅ JSON	prettier	1	0	0	0.41s
✅ JSON	v8r	1		0	3.23s
✅ REPOSITORY	checkov	yes		no	16.13s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ TSX	eslint	1	0	0	3.72s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.