A monorepo, muhahahahahaha. See the monorepo design doc for reasoning.
Package | Version | Dependencies |
---|---|---|
@babel/core |
||
@babel/parser |
||
@babel/traverse |
||
@babel/generator |
@babel/core
is the Babel compiler itself; it exposes the babel.transform
method, where transformedCode = transform(src).code
.
The compiler can be broken down into 3 parts:
- The parser:
@babel/parser
- The transformer[s]: All the plugins/presets
- These all use
@babel/traverse
to traverse through the AST
- These all use
- The generator:
@babel/generator
The flow goes like this:
input string -> @babel/parser
parser -> AST
-> transformer[s] -> AST
-> @babel/generator
-> output string
Check out the babel-handbook
for more information on this.
Package | Version | Dependencies |
---|---|---|
@babel/cli |
||
@babel/types |
||
@babel/polyfill |
||
@babel/runtime |
||
@babel/register |
||
@babel/template |
||
@babel/helpers |
||
@babel/code-frame |
@babel/cli
is the CLI tool that runs@babel/core
and helps with outputting to a directory, a file, stdout and more (also includes@babel/node
cli). Check out the docs.@babel/types
is used to validate, build and change AST nodes.@babel/polyfill
is literally a wrapper aroundcore-js
and regenerator-runtime. Check out the docs.@babel/runtime
is similar to the polyfill except that it doesn't modify the global scope and is to be used with@babel/plugin-transform-runtime
(usually in library/plugin code). Check out the docs.@babel/register
is a way to automatically compile files with Babel on the fly by binding to Node.jsrequire
. Check out the docs.@babel/template
is a helper function that allows constructing AST nodes from a string presentation of the code; this eliminates the tedium of using@babel/types
for building AST nodes.@babel/helpers
is a set of pre-made@babel/template
functions that are used in some Babel plugins.@babel/code-frame
is a standalone package used to generate errors that print the source code and point to error locations.
After Babel 6, the default transforms were removed; if you don't specify any plugins/presets, Babel will just return the original source code.
The transformer[s] used in Babel are the independent pieces of code that transform specific things. For example: the es2015-arrow-functions
transform specifically changes arrow functions into regular functions. A preset is simply an array of plugins that make it easier to run a whole a set of transforms without specifying each one manually.
Package | Version | Dependencies | Description |
---|---|---|---|
@babel/preset-env |
automatically determines plugins and polyfills you need based on your supported environments |
You can find community maintained presets on npm
Plugins are the heart of Babel and what make it work.
You can find community plugins on npm.
There are many kinds of plugins: ones that convert ES6/ES2015 to ES5, transform to ES3, minification, JSX, flow, experimental features, and more. Check out our website for more.
These just enable the transform plugins to be able to parse certain features (the transform plugins already include the syntax plugins so you don't need both): @babel/plugin-syntax-x
. Check out our website for more.
These are mostly for internal use in various plugins: @babel/helper-x
.