Upgrade @reach/router to react-router@6

Storybook uses reach/router in a few critical place places. Reach router is EOL, and unfortunately not receving much attention today (like react 17 support for the time being).

The long term path forward for reach/router is react-router6. The short term path forward is react 17 support for reach.

I attempted to start a PR to port over to react-router6, but unfortunately after a few hours determined its a bit more involved than I am capable with the context I currently posses (subtle changes like navigate coming from a hook instead of an export now, type changes and the use of definitely typed, existing storybook workarounds and wrappers for reach/router etc).

I’m opening this issue to raise awareness of upstream changes that will probably need to be addressed here at some point.

Relavant links:

Reach Router and it’s sibling project React Router are merging as React Router v6. In other words, Reach Router v2 and React Router v6 are the same. There is more information on the maintainers website. –reach.tech/router/

• https://reacttraining.com/blog/reach-react-router-future/
• https://reacttraining.com/blog/react-router-v6-pre/
• https://reacttraining.com/blog/react-router-v5-1/
• https://github.com/ReactTraining/react-router/blob/dev/docs/advanced-guides/migrating-reach-to-6.md (Migration guide)

[shilman]

w00t!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.4.0-beta.20 containing PR #16440 that references this issue. Upgrade today to the @next NPM tag to try it out!

npx sb upgrade --prerelease

Closing this issue. Please re-open if you think there’s still more to do.

[ndelangen]

going to attempt to migrate to react-router