Babel Preset Stage 2 simplifies incorporating cutting-edge JavaScript features still under standardization into your projects. Version 6.16.0 builds upon the solid foundation of 6.13.0, delivering key updates and refined functionality for developers eager to experiment with upcoming ECMAScript proposals.
A core enhancement lies in its updated dependencies. Version 6.16.0 upgraded babel-preset-stage-3 to ^6.16.0, ensuring that the features moving closer to standardization are aligned and compatible. Most notably, versions 6.16.0 upgrades babel-plugin-transform-class-properties and babel-plugin-transform-object-rest-spread, by incorporating babel-plugin-transform-async-generator-functions ensuring broader support for modern JavaScript syntax. These plugins enable developers to use class properties, object rest/spread syntax, and async generator functions without waiting for full browser support.
While retaining the foundational features related to decorators, the newer version delivers a more cohesive and consistent experience by aligning with the latest proposals. Developers upgrading to 6.16.0 benefit from these dependency updates, which provide improved stability, bug fixes, and potentially enhanced performance when transpiling features. By keeping up with the latest stage 2 proposals, developers can use it explore new language features, and give feedback on them before they are standardized. The MIT license ensures flexibility in integrating this preset into various projects, promoting widespread adoption and community contributions.
All the vulnerabilities related to the version 6.16.0 of the package
Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code
Using Babel to compile code that was specifically crafted by an attacker can lead to arbitrary code execution during compilation, when using plugins that rely on the path.evaluate()or path.evaluateTruthy() internal Babel methods.
Known affected plugins are:
@babel/plugin-transform-runtime@babel/preset-env when using its useBuiltIns option@babel/helper-define-polyfill-provider, such as babel-plugin-polyfill-corejs3, babel-plugin-polyfill-corejs2, babel-plugin-polyfill-es-shims, babel-plugin-polyfill-regeneratorNo other plugins under the @babel/ namespace are impacted, but third-party plugins might be.
Users that only compile trusted code are not impacted.
The vulnerability has been fixed in @babel/traverse@7.23.2.
Babel 6 does not receive security fixes anymore (see Babel's security policy), hence there is no patch planned for babel-traverse@6.
@babel/traverse to v7.23.2 or higher. You can do this by deleting it from your package manager's lockfile and re-installing the dependencies. @babel/core >=7.23.2 will automatically pull in a non-vulnerable version.@babel/traverse and are using one of the affected packages mentioned above, upgrade them to their latest version to avoid triggering the vulnerable code path in affected @babel/traverse versions:
@babel/plugin-transform-runtime v7.23.2@babel/preset-env v7.23.2@babel/helper-define-polyfill-provider v0.4.3babel-plugin-polyfill-corejs2 v0.4.6babel-plugin-polyfill-corejs3 v0.8.5babel-plugin-polyfill-es-shims v0.10.0babel-plugin-polyfill-regenerator v0.5.3