-
Notifications
You must be signed in to change notification settings - Fork 5
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@13 #47
Comments
I literally just did this for Opportunity Hack. I can do it here to: opportunity-hack/frontend-ohack.dev#45 |
@newswim, were y'all planning on doing any server side rendering? |
@newswim, what does success look like on this? Is it just a straightforward "Use Next 13" now? |
Hello @rstackhouse. Thank you for asking if you can contribute to this issue. I'm currently assigned to this task and I am finishing up everything for it now. I must have been unassigned to it when the milestones for the website repo were updated a few weeks ago. We have some more issues that we need help with inside this repo which you can contribute to if you can. Hope that helps |
Next.js has also received an update to their framework. It is currently at Next 14. https://nextjs.org/docs/app/building-your-application/upgrading/version-14 Should I upgrade the site repo to Next 14 or leave it on Next 13? Some dependencies need to get updated on the site's repo too. Please let me know if you want those new updates added as well. |
Hey everyone, sorry I've been on an extended hiatus from OA stuff after starting a new job. I don't think we need SSR, @rstackhouse, but the site is currently served from Vercel, so it's kind of up to the person who wants to do this upgrade. I think it might just represent additional work that we don't really need since we're not loading that much markup on the client. Another factor is our use of Chakra UI. I'm not sure how well it'll play with SSR, especially in the context of the new |
Comes with a lot of perks, including better font support. The person working this ticket should be able to follow https://beta.nextjs.org/docs/upgrade-guide.
The text was updated successfully, but these errors were encountered: