Package Exports
- babel-preset-stage-2
- babel-preset-stage-2/package.json
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (babel-preset-stage-2) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
babel-preset-stage-2
Babel preset for stage 2 plugins.
The gist of Stage 2 is:
Stage 2: draft
What is it? A first version of what will be in the specification. At this point, an eventual inclusion of the feature in the standard is likely.
What’s required? The proposal must now additionally have a formal description of the syntax and semantics of the feature (using the formal language of the ECMAScript specification). The description should be as complete as possible, but can contain todos and placeholders. Two experimental implementations of the feature are needed, but one of them can be in a transpiler such as Babel.
What’s next? Only incremental changes are expected from now on.
Install
npm install --save-dev babel-preset-stage-2
Usage
Via .babelrc
(Recommended)
.babelrc
{
"presets": ["stage-2"]
}
Via CLI
babel script.js --presets stage-2
Via Node API
require("babel-core").transform("code", {
presets: ["stage-2"]
});
References
- Chapter "The TC39 process for ECMAScript features" in "Exploring ES2016 and ES2017" by Axel Rauschmayer