babel-plugin-transform-es2015-modules-umd weekly downloads statistics
By babel (204 listings) · npm · Babel plugins
This plugin transforms ES2015 modules to UMD
babel-plugin-transform-es2015-modules-umd has 576,005 recorded weekly downloads on npm, a decrease of 53.3% over the past 30 days.
It ranks #244 of 2,256 tracked npm listings by weekly downloads.
Over 90 days, weekly downloads changed by -58.0%.
PluginStats has 121 daily observations since Jun 19, 2026; the latest is from Oct 17, 2026.
About babel-plugin-transform-es2015-modules-umd
babel-plugin-transform-es2015-modules-umd
This plugin transforms ES2015 modules to Universal Module Definition (UMD).
Example
In
Out
Installation
Usage
Via .babelrc (Recommended)
.babelrc
You can also override the names of particular libraries when this module is running in the browser. For example the es6-promise library exposes itself as global.Promise rather than global.es6Promise. This can be accommodated by:
Default semantics
There are a few things to note about the default semantics.
_First_, this transform uses the basename of each import to generate the global names in the UMD output. This means that if you're importing multiple modules with the same basename, like:
it will transpile into two references to the same browser global:
If you set the plugin options to:
it will still transpile both to one browser global:
because again the transform is only using the basename of the import.
_Second_, the specified override will still be passed to the toIdentifier function in babel-types/src/converters. This means that if you specify an override as a member expression like:
this will _not_ transpile to factory(global.fizz.buzz). Instead, it will transpile to factory(global.fizzBuzz) based on the logic in toIdentifier.
_Third_, you cannot override the exported global name.
More flexible semantics with exactGlobals: true
All of these behaviors can limit the flexibility of the globals map. To remove these limitations, you can set the exactGlobals option to true. Doing this instructs the plugin to:
1. always use the full import string instead of the basename when generating the global names 2. skip passing globals overrides to the toIdentifier function. Instead, they are used exactly as written, so you will get errors if you do not use valid identifiers or valid uncomputed (dot) member expressions. 3. allow the exported global name to be overridden via the globals map. Any override must again be a valid identifier or valid member expression.
Thus, if you set exactGlobals to true and do not pass any overrides, the first example of:
will transpile to:
And if you set the plugin options to:
then it'll transpile to:
Finally, with the plugin options set to:
it will transpile to:
Via CLI
Via Node API
Description from the npm listing.
- babel-plugin
Charts
Images: 30d · 1y · all time · 1600×900 dark
Adoption over time
7/30/90-day growth
Ranking history
Listing placement
Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.
Each band is one page of 20. Weekly downloads on a log scale. Placement is projected from weekly downloads, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.
Recent observations
Full history (121)Similar npm Babel plugins plugins
All 20 babel-plugin-transform-es2015-modules-umd alternativesData source
Weekly downloads (trailing 7 complete days) come from the official npm downloads API. Downloads include CI and mirrors and are not equivalent to installs or users. npm publishes no ratings.
Listing: https://www.npmjs.com/package/babel-plugin-transform-es2015-modules-umd. First seen Oct 16, 2026; last successful collection Oct 19, 2026. See the methodology.