Fixes #233 by reading the current location from history/navigator when updating values. For React Router 6, this involved using an internal context to access the "navigator" (history) directly, so this may become a bit flaky in the future but seems unlikely.
Fixes #233 by reading the current location from history/navigator when updating values. For React Router 6, this involved using an internal context to access the "navigator" (history) directly, so this may become a bit flaky in the future but seems unlikely.