- Upgrade all dependencies to address security alerts.
- Upgrade all dependencies to address security alerts.
- Upgrade all dependencies to address security alerts.
- Memo the navigate function returned by useNavigate()
- Upgrade all dependencies to address security alerts.
- Upgrade all dependencies to address security alerts.
- Upgrade all dependencies.
- Switch from babel to swc.
- Allow overriding automatic
currentbehaviour with an explicitcurrentprop
- Add
useMakeHrefthat returnsmakeHreffunction for creating hrefs - Breaking: rename
useLinktouseLinkProps - Breaking: rename
useRoutertouseInternalRouterInstanceto discourage use of it
- Upgrade to the latest
space-routerwhich allowsnavigateto take astringurl - Align
useLinkAPI with the rest of the router, it takes astringor anobjectnow, which is the same as hownavigateworks
- Remove async route
resolverfeature anduseNextRoute- can be implemented in userland. Previously,useNextRoutewas used in<Navigate />to know if the router is in the process of navigating, but now we use local state for that. This allowed removinguseNextRoute, and soresolvercan now be more easily implemented in userland viaonNavigating, which can block and allows processing matched routes in any way, such as awaiting ondata.component = await data.resolver(). All in all, removing API surface is great, less is more, and async route resolving is getting superseded by Suspense anyway. - Fix the webpack bundling issues caused by
setImmediateusage inspace-router. - Fix
onNavigatedcallback, which wasn't getting called correctly previously.
Ladies and gentlemen we are floating in space