-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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(nextjs): upgrade Next.js 14.0.3 #20334
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit fe3c383. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 2 targetsSent with 💌 from NxCloud. |
@zenvanexus I think you need to update the packages in main package.json file |
@gperdomor Hey thanks for your reply. The weird thing is that this didn't error out when I ran the usual steps before committing and pushing upwards. But I can do that then. |
@zenvanexus can you rebase the MR? please |
Next 14 has been out for more than 1 month, could we go on with this upgrade ? |
fe3c383
to
7a9a6a3
Compare
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 6057bda. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
4a666f8
to
51f84c2
Compare
51f84c2
to
6057bda
Compare
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
next
andeslint-config-next
to14.0.3
closed #20226
Current Behavior
@nx/next
generates theNext.js
13Expected Behavior
We should upgrade to
Next.js
14Related Issue(s)
Fixes #20226
EDIT: Related PR: #20703