-
Notifications
You must be signed in to change notification settings - Fork 27.6k
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
fix: using punycode from punycode repo and not native node #75394
base: canary
Are you sure you want to change the base?
Conversation
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
Failing test suitesCommit: 8794542
Expand output● AMP Validation on Export › production mode › should have shown errors during build
Read more about building and testing Next.js in contributing.md. |
Stats from current PRDefault BuildGeneral
Client Bundles (main, webpack)
Legacy Client Bundles (polyfills)
Client Pages
Client Build Manifests
Rendered Page Sizes
Edge SSR bundle Size
Middleware size
Next Runtimes
build cache
Diff detailsDiff for main-HASH.jsDiff too large to display |
@ijjk I noticed that the check if precompiled libs are identical before/after build was failing, so I added the punycode replacement to the ncc task itself as well |
@ijjk hey, what is going on with the checks? Do they need to be manually approved? Can we move forward with this? |
@wowczarczyk I just realized we were solving the same thing! I integrated the idea behind your change in my PR, albeit in a slightly more straightforward way here #75741. |
Sounds good, I tried to be as delicate and non-invasive as possible with the code changes but yeah, your approach seems better in the long run. Cool stuff, thanks! 🙌 |
The precompiled node-fetch was requiring the deprecated native punycode module
fixes #75313