Enhancement: remove regenerator runtime from any code that'll end up on the client

timruffles commented 5 years ago

Feature request

NextJS currently bundles regenerator-runtime in its distribution: 10k (minified) of JS that it doesn't need to. This is bad:

mobile clients, especially lower powered ones in emerging markets, struggle to parse giant chunks of JS
Next.js as a SSR framework is often picked by precisely the teams that care about performance
browsers are considering limits on JS due to the performance impact of too much JS

Therefore Next.js should remove this dependency. It's well worth the payoff for library code to avoid async and use promises directly.

Describe alternatives you've considered

As it's part of the distribution, it's unreasonably hard to remove as an end-user of Next.js.

Additional context

I'm seeing regenerator-runtime end up in client-side built code in router/index.js and lib/utils.js.
1291 mentioned this'd be coming after preset env support.

timneutkens commented 5 years ago

Still wondering why the issue templates are not being used 🤔

Just for context this issue entails the Next.js codebase itself, not the bundling of user code 🕵️

timruffles commented 5 years ago

Still wondering why the issue templates are not being used

@tim-phillips my bad, fixed.

tim-phillips commented 5 years ago

Too many Tim’s

timneutkens commented 5 years ago

One can never have too many Tims 🚀

acjay commented 5 years ago

Is it possible to manually configure Next.js to use native async support? I'm experimenting, but can't figure out how to do so.

timneutkens commented 4 years ago

Closing in favor of #7563

balazsorban44 commented 2 years ago

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.

vercel / next.js