chore: Update version for release (pre)

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release-v6.4.0-pre.13, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

release-v6.4.0-pre.13 is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on release-v6.4.0-pre.13.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

[email protected]

Patch Changes

• 815e1d1: feat: add relative=path option for url-relative routing (feat: add relative=path option for url-relative routing #9160)

  Adds a relative=path option to navigation aspects to allow users to opt-into paths behaving relative to the current URL instead of the current route hierarchy. This is useful if you're sharing route patterns in a non-nested for UI reasons:

  // Contact and EditContact do not share UI layout
  <Route path="contacts/:id" element={<Contact />} />
  <Route path="contacts:id/edit" element={<EditContact />} />
  
  function EditContact() {
    return <Link to=".." relative="path">Cancel</Link>
  }

  Without this, the user would need to reconstruct the contacts/:id url using useParams and either hardcoding the /contacts prefix or parsing it from useLocation.

  This applies to all path-related hooks and components:

  • react-router: useHref, useResolvedPath, useNavigate, Navigate
  • react-router-dom: useLinkClickHandler, useFormAction, useSubmit, Link, Form
  • react-router-native: useLinkPressHandler, Link

• Updated dependencies [e8dda1b]

• Updated dependencies [5c8fdec]

• Updated dependencies [1dc082c]

• Updated dependencies [d0114e2]

  • @remix-run/[email protected]

[email protected]

Patch Changes

• 5c8fdec: fix: pass useMatches objects to ScrollRestoration getKey (fix: pass useMatches objects to ScrollRestoration getKey #9157)

• 815e1d1: feat: add relative=path option for url-relative routing (feat: add relative=path option for url-relative routing #9160)

  Adds a relative=path option to navigation aspects to allow users to opt-into paths behaving relative to the current URL instead of the current route hierarchy. This is useful if you're sharing route patterns in a non-nested for UI reasons:

  // Contact and EditContact do not share UI layout
  <Route path="contacts/:id" element={<Contact />} />
  <Route path="contacts:id/edit" element={<EditContact />} />
  
  function EditContact() {
    return <Link to=".." relative="path">Cancel</Link>
  }

  Without this, the user would need to reconstruct the contacts/:id url using useParams and either hardcoding the /contacts prefix or parsing it from useLocation.

  This applies to all path-related hooks and components:

  • react-router: useHref, useResolvedPath, useNavigate, Navigate
  • react-router-dom: useLinkClickHandler, useFormAction, useSubmit, Link, Form
  • react-router-native: useLinkPressHandler, Link

• 6fef589: fix: useFormAction should not include pathless splat portion (fix: useFormAction should not include pathless splat portion #9144)

• Updated dependencies [815e1d1]

  • [email protected]

[email protected]

Patch Changes

• Updated dependencies [5c8fdec]
• Updated dependencies [815e1d1]
• Updated dependencies [6fef589]
  • [email protected]
  • [email protected]

[email protected]

Patch Changes

• 815e1d1: feat: add relative=path option for url-relative routing (feat: add relative=path option for url-relative routing #9160)

  Adds a relative=path option to navigation aspects to allow users to opt-into paths behaving relative to the current URL instead of the current route hierarchy. This is useful if you're sharing route patterns in a non-nested for UI reasons:

  // Contact and EditContact do not share UI layout
  <Route path="contacts/:id" element={<Contact />} />
  <Route path="contacts:id/edit" element={<EditContact />} />
  
  function EditContact() {
    return <Link to=".." relative="path">Cancel</Link>
  }

  Without this, the user would need to reconstruct the contacts/:id url using useParams and either hardcoding the /contacts prefix or parsing it from useLocation.

  This applies to all path-related hooks and components:

  • react-router: useHref, useResolvedPath, useNavigate, Navigate
  • react-router-dom: useLinkClickHandler, useFormAction, useSubmit, Link, Form
  • react-router-native: useLinkPressHandler, Link

• Updated dependencies [815e1d1]

  • [email protected]

@remix-run/[email protected]

Patch Changes

• e8dda1b: fix: avoid uneccesary re-renders on defer resolution (fix: avoid uneccesary re-renders on defer resolution #9155)
• 5c8fdec: fix: pass useMatches objects to ScrollRestoration getKey (fix: pass useMatches objects to ScrollRestoration getKey #9157)
• 1dc082c: fix: fetcher submission revalidating fetchers using wrong key (fix: fetcher submission revalidating fetchers using wrong key #9166)
• d0114e2: fix: use a push navigation on submission errors (fix: use a push navigation on submission errors #9162)