Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Next App Router (version 13.4) #327

Closed
andreisocaciu opened this issue May 12, 2023 · 3 comments
Closed

Support for Next App Router (version 13.4) #327

andreisocaciu opened this issue May 12, 2023 · 3 comments

Comments

@andreisocaciu
Copy link
Contributor

Hi,

I use this library in my own projects and I was curious if there are any plans to add support for the new app directory that is now stable in Next 13.4.

The main issue is that the useRouter from 'next/router' is no longer supported in the app directory and it makes using this library impossible. It is being replaced by the useRouter from 'next/navigation', together with usePathname and useSearchParams.

@franky47
Copy link
Member

Eventually, yes, though I suppose this will require a major version bump because of the breaking changes you mention, or some sort of dual export to target either the pages or app routers.

That being said, with Next.js becoming more and more of a server-first framework, I expect a lot of hurdles along the way.

If you'd like to open a PR, I will gladly review it.

andreisocaciu added a commit to andreisocaciu/next-usequerystate that referenced this issue May 15, 2023
@github-actions
Copy link

🎉 This issue has been resolved in version 1.8.0-beta.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 This issue has been resolved in version 1.8.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants