Babel Preset Env simplifies JavaScript transpilation by intelligently determining the necessary Babel plugins based on your target environments. Versions 1.1.6 and 1.1.7, though seemingly similar, offer subtle nuances crucial for developers optimizing their build processes. A key benefit of using babel-preset-env is to avoid including all babel plugins, making the build faster and the final bundle smaller in size.
Both versions share a core set of dependencies, including various babel-plugin-transform-* packages, ensuring support for modern JavaScript features. These handle transformations like arrow functions, classes, destructuring, and more to maintain compatibility with older browsers and environments. The browserslist dependency is also present, allowing you to specify target browsers for babel-preset-env. Use of this library will result in the inclusion of only the plugins you need to support the browsers you are targeting improving the compilation speed.
The primary difference lies in the releaseDate. Version 1.1.7 was released on January 9, 2017, while version 1.1.6 came out on January 6, 2017. While the direct impact of this difference might not be immediately apparent from the provided data, it implies potential bug fixes, performance improvements, or minor feature enhancements incorporated in the newer version. Users should prioritize using the later version as it represents the most current stable release. It ensures access to the latest refinements, enhancing reliability and potentially optimizing performance within your development workflow. For projects already using version 1.1.6, upgrading to 1.1.7 is generally recommended to leverage these underlying improvements and keep dependencies up to date.
All the vulnerabilities related to the version 1.1.7 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