* chore: clean up changes
* feat: clean up work and address feedback
* feat: add backwards compat
* ci: apply automated fixes
* feat: give history action to subscribers via notify
* fix: provide go index to history subscribers
* docs: updated docs accourding to feedback
* fix: changed valid notify call
* rename to `type`
* remove non existing `pushstate`event
* cleanup
* typesafe API for shouldBlockFn
* feat: added blocking state to resolver and updated examples
* docs: updated useBlocker and navigation-blocking docs
* test: added type tests to blocker and changed type implementation of blocker
* test: added better unit tests for useBlocker hook
* test: added e2e tests for blocker and legacy blocker
* wip: stash files before merge
* fix: unstashed e2e file after merge
* fix lockfile
* docs
* typesafety for `<Block>`
* always return resolver to not break backwards compatibility
* fix: removed zod from navigation blocking example to fix build problem
* chore: update lock file
* finishing touches
* ci: apply automated fixes
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Manuel Schiller <manuel.schiller@caligano.de>
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