Because it's more accessible, smaller, and generally I think more my scene, I'd like to switch to @reach/router as our "default" router for react-dom. Because on the React Native side I'd likely prefer react-navigation anyway I think it's fine to "ditch" react-router.
I'd like to switch any documentation and API assumptions over to @react/router.
Actually, we'll be preferring no router. In our own projects I think we'll use @reach/router, but for now we're just accepting props and passing them through.
Because it's more accessible, smaller, and generally I think more my scene, I'd like to switch to
@reach/router
as our "default" router forreact-dom
. Because on the React Native side I'd likely preferreact-navigation
anyway I think it's fine to "ditch"react-router
.I'd like to switch any documentation and API assumptions over to
@react/router
.