-
-
Notifications
You must be signed in to change notification settings - Fork 39
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 11 #324
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/drewclem/protege/A7V9AsHvXDTnHgREkhUUhiP4jPnU |
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.
looks good!
@drewclem, I can’t see the Vercel logs. Is the error a valid error because of the upgrade or is it unrelated? |
On build now with NEXT.js 11, eslint runs as part of the build. Currently it's erroring out with the following lint errors. Let's open a separate issue to fix the lint errors and once those are sorted we'll reenable linting on build.
|
Description
Upgrades the project to NEXT.js 11. I went through the upgrade guide and a bunch of it doesn't apply to the project, or we already made the necessary changes when we first added NEXT.js to the project.
Related Tickets and Documents
Closes #323
What gif best describes this PR or how it makes you feel? (optional)