-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
build(deps): bump Next to v14 with Netlify build Workaround #12266
build(deps): bump Next to v14 with Netlify build Workaround #12266
Conversation
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
…deployed functions
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.
🚀
"node_modules/next/dist/server/future/route-modules/pages/vendored/contexts/amp-context*", | ||
"node_modules/next/dist/server/future/route-modules/pages/vendored/contexts/head-manager-context*", | ||
] |
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.
@pettinarip Great! This is kinda insane to have to do all of that configuring. 😅 |
Yeah, right? all the nuances you have to deal with 🤷🏼 the cost of living on the edge :P |
Description
Upgrades NextJs to v14.
Two main changes added to avoid problems with the build:
process.cwd()
in a function, otherwise the Netlify runtime plugin would for some reason bundle the entire project folder, causing the deploy to fail due to size limits (250mb max).public
folder from the deployed functions by using more specific syntax:[functions.{function-name}]
instead of just[functions]
.