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

Upgrade to Next.js 13 #65

Closed
sawyerh opened this issue Oct 25, 2022 · 0 comments · Fixed by #69
Closed

Upgrade to Next.js 13 #65

sawyerh opened this issue Oct 25, 2022 · 0 comments · Fixed by #69
Assignees

Comments

@sawyerh
Copy link
Contributor

sawyerh commented Oct 25, 2022

https://nextjs.org/blog/next-13

@sawyerh sawyerh self-assigned this Oct 31, 2022
sawyerh added a commit that referenced this issue Nov 1, 2022
## Ticket

Closes #65

## Context for reviewers

Next.js 13 introduced [pretty significant new
functionality](https://nextjs.org/blog/next-13), but it's backwards
compatible with the existing approach implemented in this repo, so
should be safe to upgrade. Projects can adopt its new functionality as
they want. We have a separate ticket for adopting the new functionality
in this repo: #66
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant