Router Context is provided but matchContext is not
Having a weird issue that appeared out of blue without noticeable changes. Using Link throws errors
can't access property "routeId" of undefined as in useMatch the const nearestMatchId = React.useContext(matchContext); always results in undefined. Considering that the Match Context is always a part of Outlet, why could it happen?1 Reply
fair-roseOP•2y ago
I'm not sure the fact that some of those components are in the root route component
And the elephant in the room is that Webpack Federation Plugin is used but it doesn't cause typical federation problems as the Router context is shared properly.