Rollup-plugin-ts has seen a minor version bump from 1.2.8 to 1.2.10, offering improvements for developers using TypeScript with Rollup. The core functionality remains consistent: the plugin efficiently bundles TypeScript code, generates declaration files, and respects Browserslist configurations for optimal browser compatibility.
A key difference lies in the updated dependencies. Version 1.2.10 features specific versions of Babel packages like @babel/core, @babel/runtime, @babel/preset-env, @babel/plugin-transform-runtime, @babel/plugin-proposal-json-strings, @babel/plugin-syntax-dynamic-import, @babel/plugin-proposal-object-rest-spread, @babel/plugin-proposal-optional-catch-binding, @babel/plugin-proposal-unicode-property-regex, and @babel/plugin-proposal-async-generator-functions all pinned to 7.7.x versions. In contrast, version 1.2.8 utilized newer 7.8.x versions signifying a deliberate choice in 1.2.10 to either maintain compatibility or address any regressions introduced in later Babel releases.
While the core functionality remains the same, developers should examine if this deliberate downgrade might interact with their babel configuration and pipeline. The updated dependencies ensure more stable and predictable behavior across different environments. The peer dependencies remain the same which signify that both versions are still compatible with the same versions of rollup and typescript.
All the vulnerabilities related to the version 1.2.10 of the package
Babel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups
When using Babel to compile regular expression named capturing groups, Babel will generate a polyfill for the .replace method that has quadratic complexity on some specific replacement pattern strings (i.e. the second argument passed to .replace).
Your generated code is vulnerable if all the following conditions are true:
.replace method on a regular expression that contains named capturing groups.replaceIf you are using @babel/preset-env with the targets option, the transform that injects the vulnerable code is automatically enabled if:
You can verify what transforms @babel/preset-env is using by enabling the debug option.
This problem has been fixed in @babel/helpers and @babel/runtime 7.26.10 and 8.0.0-alpha.17, please upgrade. It's likely that you do not directly depend on @babel/helpers, and instead you depend on @babel/core (which itself depends on @babel/helpers). Upgrading to @babel/core 7.26.10 is not required, but it guarantees that you are on a new enough @babel/helpers version.
Please note that just updating your Babel dependencies is not enough: you will also need to re-compile your code.
If you are passing user-provided strings as the second argument of .replace on regular expressions that contain named capturing groups, validate the input and make sure it does not contain the substring $< if it's then not followed by > (possibly with other characters in between).
This vulnerability was reported and fixed in https://github.com/babel/babel/pull/17173.