Missing polyfills and transforms for older browsers

[kripod]

Bug report

Describe the bug

While browsing the polyfills applied by Next.js 9.5.1, I encountered a lot of features which aren't polyfilled:

ES2015

• Number.{parseFloat,parseInt}
• Math.{acosh,asinh,atanh,cbrt,clz32,cosh,expm1,fround,hypot,imul,log10p,log1p,log2,sign,sinh,tanh,trunc}

ES2019

• Object.fromEntries

ES2020

• String.prototype.matchAll

ES2021

• String.prototype.replaceAll
• Promise.any + AggregateError
• WeakRef

This may cause unnoticed issues in various browsers.

Missing Babel transforms

• globalThis should be transformed into window in browser environments
• export * as ns from 'module' should be transformed with Babel
• import.meta should be supported (e.g. for standards-compilant hot module replacement)

Expected behavior

The features above should be supported to avoid browser compatibility issues.

Warnings for non-polyfilled features

There are some features which cannot be polyfilled (or it's hard to do so). For those, an ESLint config or console warnings should be made:

• Proxy
• Atomics
• SharedArrayBuffer
• RegExp lookbehind assertions: (?<= ) and (?<! )
• BigInt

[eddyw]

I raised a similar issue a while ago #10966

Bottom line is that NextJS ships with just enough polyfills to get it running >=IE11 but you need to add polyfills for other features that you'll use in your app.

[kripod]

@eddyw Thanks for the feedback! I've just opened a new PR to fix most of the outlined issues with no significant bundle size changes.

[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.