rauschma/preset-env-usebuiltins.md

Last active April 8, 2018 02:25

Star (5) You must be signed in to star a gist
Fork (3) You must be signed in to fork a gist

Select an option

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/rauschma/fc6973110700c4932d360d5eb6ad9931.js"></script>
Save rauschma/fc6973110700c4932d360d5eb6ad9931 to your computer and use it in GitHub Desktop.

Download ZIP

Raw

preset-env-usebuiltins.md

Browsers

Approach for untranspiled code:

No package ever polyfills.
- Use only functionality at stage 4 or older.
The entry point does import "babel-polyfill"; for which env.useBuiltins generates the imports appropriate for the current targets.
- Benefit: the bundle only includes functionality that the target platforms don’t have. Think: custom-tailored babel-polyfill.

Node.js

For Node.js, the untranspiled code would be transpiled via target: { node: "current" }.

Play it safe, should every package do import "babel-polyfill"; at its entry point?
- Note: not as problematic, because bundle size is not a factor on Node.js.

prichodko commented Jul 25, 2017

First of all, thanks for this gist!
I have two question, I'd like to clarify. Does babel-polyfill include regeneratorRuntime? And how to deal with a situation, when a library has to support browser and node.js?

Author

rauschma commented Jul 25, 2017

babel-polyfill does include regenerator-runtime: https://github.com/babel/babel/blob/master/packages/babel-polyfill/package.json
The approach I linked to is for supporting both browsers and Node.js: http://2ality.com/2017/07/npm-packages-via-babel.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment