router icon indicating copy to clipboard operation
router copied to clipboard

šŸ¤– Fully typesafe Router for React (and friends) w/ built-in caching, 1st class search-param APIs, client-side cache integration and isomorphic rendering.

Results 526 router issues
Sort by recently updated
recently updated
newest added

### Which project does this relate to? Router ### Describe the bug I've noticed the pending component doesn't stay mounted if it's on the __root route. It seems like it...

### Which project does this relate to? Router ### Describe the bug There are some weird behaviors when resetting from the `errorComponent` if the loader returns both async and deferred...

### Which project does this relate to? Router ### Describe the bug The component defined in the `rootRoute` is rendered when a non-matching path riggers the rendering of the `notFoundComponent`...

bug

### Which project does this relate to? Router ### Describe the bug Iā€˜m using `` to fetch some data in a `notFoundComponent`. When using `renderToPipeableStream()` I can see the following...

bug
start

Updating server route docs example with correct endpoint in code example. Excluding the `"/api"` prefix.

### Which project does this relate to? Router ### Describe the bug By configuring the Router as below and using a `useQuery` hook on page 1 and a `fetchQuery` call...

# Proposal - https://github.com/TanStack/router/discussions/4113 # Overview This PR introduces the new `useHistoryState` hook and related functionality to enable type-safe history state management in TanStack Router. - https://github.com/TanStack/router/discussions/975#discussioncomment-10414075 - https://github.com/TanStack/router/discussions/284#discussioncomment-9344482 ##...

documentation
package: react-router
package: router-core
package: solid-router
package: router-devtools-core

The react basic-ssr-streaming-file-based example is a bit outdated and no longer working. This fix updates the server.js and entry-server.tsx to match those of the basic-ssr-file-based example as these were using...

This might be a **big change** for a tiny issue, so I'd love some opinions on this. I'm really not at all an expert on npm / semver / publishing...

This PR contains the following updates: | Update | Change | |---|---| | lockFileMaintenance | All locks refreshed | šŸ”§ This Pull Request updates lock files to use the latest...

dependencies