* refactor: inline pushComment * chore: add benchmark cases * perf: overhaul comment attachment * cleanup * update test fixtures They are all bugfixes. * fix: merge HTMLComment parsing to skipSpace * perf: remove unattachedCommentStack baseline 128 nested leading comments: 11_034 ops/sec ±50.64% (0.091ms) baseline 256 nested leading comments: 6_037 ops/sec ±11.46% (0.166ms) baseline 512 nested leading comments: 3_077 ops/sec ±2.31% (0.325ms) baseline 1024 nested leading comments: 1_374 ops/sec ±3.22% (0.728ms) current 128 nested leading comments: 11_027 ops/sec ±37.41% (0.091ms) current 256 nested leading comments: 6_736 ops/sec ±1.39% (0.148ms) current 512 nested leading comments: 3_306 ops/sec ±0.69% (0.302ms) current 1024 nested leading comments: 1_579 ops/sec ±2.09% (0.633ms) baseline 128 nested trailing comments: 10_073 ops/sec ±42.95% (0.099ms) baseline 256 nested trailing comments: 6_294 ops/sec ±2.19% (0.159ms) baseline 512 nested trailing comments: 3_041 ops/sec ±0.8% (0.329ms) baseline 1024 nested trailing comments: 1_530 ops/sec ±1.18% (0.654ms) current 128 nested trailing comments: 11_461 ops/sec ±44.89% (0.087ms) current 256 nested trailing comments: 7_212 ops/sec ±1.6% (0.139ms) current 512 nested trailing comments: 3_403 ops/sec ±1% (0.294ms) current 1024 nested trailing comments: 1_539 ops/sec ±1.49% (0.65ms) * fix: do not expose CommentWhitespace type * add comments on CommentWhitespace * add test case for #11576 * fix: mark containerNode be the innermost node containing commentWS * fix: adjust trailing comma comments for Record/Tuple/OptionalCall * fix: drain comment stacks in parseExpression * docs: update comments * add a new benchmark * chore: containerNode => containingNode * add more benchmark cases * fix: avoid finishNodeAt in stmtToDirective * finalize comment right after containerNode is set * add testcase about directive * fix: finish SequenceExpression at current pos and adjust later * chore: rename test cases * add new test case on switch statement * fix: adjust comments after trailing comma of function params * add comment attachment design doc * misc fix * fix: reset previous trailing comments when parsing async method/accessor * chore: add more comment testcases * fix flow errors * fix: handle comments when parsing async arrow * fix: handle comments when "static" is a class modifier * fix flow errors * fix: handle comments when parsing async function/do * refactor: simplify resetPreviousNodeTrailingComments * update test fixtures
Woah, what's going on here?
A monorepo, muhahahahahaha. See the monorepo design doc for reasoning.
Core Packages
| 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/traverseto 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.
Other
| Package | Version | Dependencies |
|---|---|---|
@babel/cli |
||
@babel/types |
||
@babel/runtime |
||
@babel/register |
||
@babel/template |
||
@babel/helpers |
||
@babel/code-frame |
@babel/cliis the CLI tool that runs@babel/coreand helps with outputting to a directory, a file, stdout and more (also includes@babel/nodecli). Check out the docs.@babel/typesis used to validate, build and change AST nodes.@babel/runtimeis 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/registeris a way to automatically compile files with Babel on the fly by binding to Node.jsrequire. Check out the docs.@babel/templateis a helper function that allows constructing AST nodes from a string presentation of the code; this eliminates the tedium of using@babel/typesfor building AST nodes.@babel/helpersis a set of pre-made@babel/templatefunctions that are used in some Babel plugins.@babel/code-frameis a standalone package used to generate errors that print the source code and point to error locations.
Presets
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
Plugins are the heart of Babel and what make it work.
You can find community plugins on npm.
Transform Plugins
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.
Syntax Plugins
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.
Helpers
These are mostly for internal use in various plugins: @babel/helper-x.