Scott Rippey

This sounds like a good idea, I will try to add support. PRs are welcome though, if you have a fix or some unit tests!

I do not currently have the extra bandwidth to finish this PR, I'm sorry! I'd be happy to accept incoming PRs. This PR is only partially complete. I've added support...

Yes, it should definitely be doable, but I haven't tried it out yet so there might be some gotchas. One gotcha that comes to mind: for Storybook you'll need to...

All of this should go in your `preview.js` if you intend for it to be global. Please post back if you've tried it out? I'd be happy to add this...

I believe this is due to Next's async behavior. You can import from `next-router-mock/async` to ensure the async behavior is replicated. See: https://github.com/scottrippey/next-router-mock#sync-vs-async Please let me know if this works...

The snapshot is intentional, because that does seem to be how Next behaves. If you've got a closure around the `router` and you try to access the `.query` etc, it'll...

Having said that, you're still observing a behavior that is different between `next/router` and `next-router-mock`, and I'd like to figure out what's going on. Do you think you could create...

Thanks, now I see what's happening. In Next, it appears that the `routeChangeComplete` event is triggering **after** React has re-rendered. Here's the order of events that I'm seeing: 1. Initial...

There's also one more solution for you to consider. In Next, you can also use the "singleton router" for this kind of situation. The singleton router does not use snapshots,...

I don't see anything wrong with this code, but I think it would be nice to see the implementation of ``. I think the way that `next/link` works is that...