-
Notifications
You must be signed in to change notification settings - Fork 97
fix: ensure next-server patches only run on Netlify #2117
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
Conversation
this keeps previous behavior for standalone next server
✅ 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 netlify-plugin-nextjs-nx-monorepo-demo ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for next-i18next-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-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 nextjs-plugin-custom-routes-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. |
orinokai
left a comment
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.
Nice! Thanks @zachleat, lgtm 🚢
This restores non-patched behavior for standalone next server.
Description
When you run
next devstandalone afternetlify devhas patched Next files, it can skip middleware and other configuration. This makes the patches a little more defensive, requiringprocess.env.NETLIFYto be in place. This is important as the other ENV variable checks were!== 'true'which successfully passed whennext devwas in use.Tests
This test case was validated https://github.com/anthonyholmes/next-netlify-middleware-bug (noting that step 6 in the readme is inaccurate)
Relevant links (GitHub issues, etc.) or a picture of cute animal
Fixes netlify/pod-ecosystem-frameworks#474