Babel-preset-react-app is a crucial dependency for Create React App projects, streamlining Babel configuration for modern JavaScript development. Comparing versions 1.0.0 and 2.0.0 reveals key updates affecting transpilation and optimization. Both versions share core components like babel-runtime, babel-preset-react, babel-preset-latest, babel-plugin-transform-runtime, babel-plugin-transform-regenerator, babel-plugin-transform-react-jsx-self, babel-plugin-transform-class-properties, babel-plugin-transform-react-jsx-source, andbabel-plugin-transform-react-constant-elements, laying the foundation for JSX transformation, class property support, and performance enhancements.
However, version 2.0.0 introduces babel-plugin-transform-object-rest-spread version 6.19.0, a later version than the one used in version 1.0.0 (6.16.0). Version 1.0.0 also includes babel-plugin-transform-es2015-parameters and babel-plugin-transform-es2015-destructuring, which are not present in version 2.0.0. This suggests adjustments in how ES2015 features are handled, potentially streamlining the preset or delegating these transformations to other plugins or preset-env configurations. Furthermore, babel-preset-env is updated from version 0.0.6 to 0.0.8, indicating improvements in environment-based polyfilling and transpilation.
For developers, version 2.0.0 likely offers a more refined and potentially more efficient Babel configuration, optimizing for the evolving landscape as it includes a more recent version of babel-plugin-transform-object-rest-spread. The changes in ES2015 transformation handling might impact compatibility or performance depending on the codebase and target environments. Developers should evaluate these differences to ensure a smooth upgrade and optimal build process. Always consult the official Create React App documentation for the most up-to-date guidance.
All the vulnerabilities related to the version 2.0.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