Optimize Next.js polyfilling behavior (Babel)

[Timer]

Next.js appears to polyfill runtime behavior using transform-runtime rather than preset-env.

This typically creates more bundle code than the useBuiltIns alternative, so we should look at using { helpers: true, useBuiltIns: true } or the most optimized configuration we can find.

It'd also probably be a great time to create a separate polyfills chunk since they seldom change.

[StarpTech]

Is it also possible to improve the polyfill behaviour for all project dependencies? Gatsby already do this gatsbyjs/gatsby#14111 for production.

[jeroenvisser101]

Related: #8521

[timneutkens]

This was solved by https://nextjs.org/blog/next-9-1-7#new-built-in-polyfills-fetch-url-and-objectassign

[StarpTech]

This was solved by nextjs.org/blog/next-9-1-7#new-built-in-polyfills-fetch-url-and-objectassign

@timneutkens not sure if it is really fixed. Your post only refers to specific libs.

More size reduction has been accomplished by providing built-in, small polyfills for often-used packages.

This issue was about polyfill the project based on the environment requirements. Is it done?

[timneutkens]

This issue was solved over multiple versions. Transform-runtime was replaced with an alternative for useBuiltIns, I did the work for that so I'm sure this issue is fixed 😁

[StarpTech]

Great, thanks!

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.