-
Notifications
You must be signed in to change notification settings - Fork 86
feat: support Next 13 #1714
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
feat: support Next 13 #1714
Conversation
✅ Deploy Preview for netlify-plugin-nextjs-nx-monorepo-demo ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for netlify-plugin-nextjs-next-auth-demo ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for netlify-plugin-nextjs-export-demo ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for next-plugin-edge-middleware ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for netlify-plugin-nextjs-static-root-demo ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
❌ Deploy Preview for next-i18next-demo failed.
|
✅ Deploy Preview for nextjs-plugin-custom-routes-demo ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for next-plugin-canary ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for netlify-plugin-nextjs-demo ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
I've disabled Node 12 tests in branch protections. Once this is in we can start requiring the Node 14 tests instead |
@ericapisani the next/image tests are failing at the moment. The images seem to display fine, but the tests fail. I'm going to switch them to use next/legacy/image and we can look into why the new component is breaking thing. |
The I18next site is failing because it doesn't like the canary version number. Updating to 13.0.0 should fix that. |
demos/canary/pages/index.js
Outdated
@@ -1,5 +1,5 @@ | |||
import Head from 'next/head' | |||
import Image from 'next/image' | |||
import Image from 'next/legacy/image' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this temporary until the image tests get working in this PR or are we switching back to the new next/image
post this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we do it post this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look good. Assuming all checks pass, this is good to 🚀
The i18next demo will fail to build for now (until Next 13 is published to npm), but aside from that it should all be good to go. |
Summary
Updates the test sites and dependencies to Next 13 (actually 12.3.2-canary.43, but that is the same as next 13, which isn;t yet in npm)
Test plan
Relevant links (GitHub issues, Notion docs, etc.) or a picture of cute animal
Standard checks:
🧪 Once merged, make sure to update the version if needed and that it was published correctly.