both router and react 19 were modifying the Promise object in a similar manner which caused a conflict.
See https://github.com/facebook/react/blob/v19.0.0/packages/react-reconciler/src/ReactFiberThenable.js#L162-L228 for how React 19 modifies the Promise object.
Both used an additional `status` property to track the Promise status, but router was using the value "success" and React was using the value "fulfilled" to mark a fulfilled Promise.
This change stores the router specific Promise tracking values using a symbol to avoid any potential collision.
fixes#2953
* feat: return async resolver from useBlocker hook
* feat: pass async resolvers to children on Block component
* fix: types and always reset promise
* docs: update example with custom UI
* refactor: namings
* docs: toggle between custom ui and default
* feat: expose status and refactor hook props
* feat: support current API
* feat: custom blocker should take precendence over the manual promise blocker
* test: unit test on condition to avoid breaking changes with the new API
* docs: deprecate old syntax and update the docs
* docs: create useBlocker API reference
* fix: deprecated interface
* docs: add createLazyFileRoute
* docs: broken link to the FileRouteClass
* docs: remove the word literal
* docs: update the source of its configuration options
* docs: add createLazyRoute
* fix: `routeTree` into the `createRouter` instance
* fix: switch to `Block/useBlocker` since react-router uses `useBlocker` instead of `Prompt/usePrompt`
* fix: rename RouteApi to getRouteApi and include useLoaderDeps
* feat: indicate `.lazy` suffix and mark deprecation suffixes being phased out
* fix: createRootRouteWithContext - `routeTree` into the `createRouter` instance
* fix: rootRouteWithContext - `routeTree` into the `createRouter` instance
* feat: `Function` keyword is redundant since its already nested under `Functions`
* feat: alphabetical sorting of functions
* feat: move `rootRouteWithContext` to the deprecated list
* feat: use backticks
* feat: alphabetical sorting of hooks
* feat: add `notFound`, boundary, and support for routes
* feat: add global not found
* refactor: clean up throw global not found route
* feat: reset not founds on page navigation
* fix: fix duplicate throw global not found
* feat: rework global not found handling and add not-found-ssr example
* feat: update not found ssr example
* fix: fix type in not-found.tsx
* feat: add way to statically render a global not found page
* feat: remove flicker from notFound with SSR
* feat: remove <GlobalNotFound> server api
* feat: add file-based routing and codesplitting for not found component
* feat: add option to trigger not found on specific route
* docs: write docs for `notFound` and `NotFoundError`
* docs: document Route.notFound(opts)
* feat: add deprecation warnings to notFoundRoute
* fix: clean up a few things that went awry during rebase
* fix: fix react-router-server build
* feat: add not-found apis to basic-file-based example
* feat: update basic-ssr-streaming-file-based example to use new not-found apis
* chore: clean up a few things
* docs: write guides for new not found api
* docs: add api documentation for `not-found.tsx`
* feat: add notFoundComponent to lazy loading
* docs: deprecate NotFoundRoute and link to new apis
* fix: remove `.notFoundComponent` suffix in file based routing
* feat: make `route` option of typesafe and compatible with `getRouteApi`