Babel Preset Env streamlines JavaScript development by intelligently compiling code for target environments, ensuring compatibility across browsers and Node.js versions. Comparing versions 1.3.0 and 1.3.1 reveals subtle but crucial refinements. Both versions share a core set of dependencies, including a suite of Babel plugins like transform-es2015-* for transpiling ES2015 features, transform-async-to-generator for asynchronous code, and tools for block scoping, destructuring, and more. Development dependencies remain consistent, ensuring a stable testing and linting environment with tools like babel-cli, eslint, mocha, and code coverage utilities.
The key difference lies in the release date, with version 1.3.1 released shortly after 1.3.0. While the provided data doesn't explicitly detail the code changes between the versions, the rapid succession suggests that version 1.3.1 likely addresses minor bug fixes, performance improvements, or dependency updates not significant enough to warrant a major or minor version bump. For developers, the value of Babel Preset Env resides in its ability to automate browser compatibility, saving significant time and effort. By specifying target environments, Babel Preset Env intelligently includes the necessary plugins to transpile code, enabling developers to write modern JavaScript without worrying about older browsers. The MIT license ensures flexibility and freedom in using and modifying the preset. Upgrading from 1.3.0 to 1.3.1 is recommended for the latest stability improvements.
All the vulnerabilities related to the version 1.3.1 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