Scott Rippey

If `router.back` was supported, what kind of use-case would you want? Like, maybe `push` should keep a stack of URLs, and `router.back` would pop from the stack? Any other scenarios...

You're correct, every couple of versions of Next, they move this file path. I'll add next 14 support very soon. PR's welcome if you want to get to it sooner!

Where do you get this error? Storybook? Jest? I've done some tests with next 13, and so far things looked good. But I haven't looked at the new `app` infrastructure...

Regarding `MemoryRouterProvider` issues: In Next 13, they did not change any of the internal paths. So, I'm having trouble reproducing the issue. I created #66 to test the Next 13...

So there are 2 separate issues here, hopefully this message helps people # `Module not found: Error: Can't resolve 'next/dist/next-server/lib/router-context'` is solved by importing from this path instead: ``` import...

This is a great start, thank you! I've been playing with Next 13 lately, and it seems like the `next/navigation` implementation will be _mostly_ easy, since the underlying URL logic...

I've started a branch to implement these `next/navigation` hooks! I'm going to move this discussion to #103, since this thread has too many side-tracks.

Reopened for tracking purposes.

@rollercodester Thanks for that workaround! Worked for me. For anyone also having trouble with `@semantic-release`, getting an error message like `XXX is not allowed to access package @semantic-release/commit-analyzer`, here is...

Well, here's a site that does this: http://css2less.cc/ (https://github.com/thomaspierson/libcss2less) But I assumed it was client-side, but now I realize it's Ruby. I think a JS implementation is worthy of an...