Closed tom-streller-tutti closed 9 months ago
Latest commit: d2e8fffadfbdc15593593c8306cfa53b8f8e4e63
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
Merging this PR would also fix issue #111 .
@scottrippey Any chance of getting this merged? It's currently blocking a crucial update for us.
We are using the
next-router-mock/async
provider and had a bunch of issues with the Provider, as it appeared all manipulations of the router get ignored by our components.Looking into the code, I discovered why: The
<MemoryRouterProvider />
ignores theasync
prop unless anurl
is given. However, when anurl
is given, a new router is created.This should return the async singleton when requested - however, I could not test if it works for our application as I couldn't figure out how to include the package without it being published.