Tsup is a modern bundler for JavaScript and TypeScript projects, leveraging the power of Rollup and ESBuild for efficient and fast builds. Comparing versions 1.0.0 and 1.1.0 reveals subtle but important updates for developers. Both versions share the same core dependencies, including Rollup for bundling and the rollup-plugin-esbuild for incredibly fast TypeScript and JavaScript compilation. They also use the same suite of development tools, such as Cac for command-line argument parsing, resolve for module resolution, Colorette for terminal styling, and TypeScript for type checking. Crucially, the commonjs plugin is employed to easily use components using that module type.
The primary difference lies in the dist object. Specifically, version 1.1.0 has a slightly larger unpacked size (322870 bytes) compared to version 1.0.0 (322726 bytes). This suggests that version 1.1.0 incorporates minor improvements or adjustments, potentially including bug fixes, performance enhancements, or updated documentation. This small footprint difference, though seemingly insignificant, can translate to improved build times and potentially slightly faster execution in certain scenarios. Also, the release date for the 1.1.0 is slightly after the 1.0.0.
For developers considering using Tsup, either version provides a solid foundation for bundling modern JavaScript and TypeScript projects. The straightforward setup and reliance on ESBuild translate to a smoother and faster development workflow. While the functional differences between versions 1.0.0 and 1.1.0 appear minimal, it's generally recommended to opt for the latest version (1.1.0) to benefit from any incremental improvements and bug fixes.
All the vulnerabilities related to the version 1.1.0 of the package
tsup DOM Clobbering vulnerability
A DOM Clobbering vulnerability in tsup v8.3.4 allows attackers to execute arbitrary code via a crafted script in the import.meta.url to document.currentScript in cjs_shims.js components
esbuild enables any website to send any requests to the development server and read the response
esbuild allows any websites to send any request to the development server and read the response due to default CORS settings.
esbuild sets Access-Control-Allow-Origin: * header to all requests, including the SSE connection, which allows any websites to send any request to the development server and read the response.
https://github.com/evanw/esbuild/blob/df815ac27b84f8b34374c9182a93c94718f8a630/pkg/api/serve_other.go#L121 https://github.com/evanw/esbuild/blob/df815ac27b84f8b34374c9182a93c94718f8a630/pkg/api/serve_other.go#L363
Attack scenario:
http://malicious.example.com).fetch('http://127.0.0.1:8000/main.js') request by JS in that malicious web page. This request is normally blocked by same-origin policy, but that's not the case for the reasons above.http://127.0.0.1:8000/main.js.In this scenario, I assumed that the attacker knows the URL of the bundle output file name. But the attacker can also get that information by
/index.html: normally you have a script tag here/assets: it's common to have a assets directory when you have JS files and CSS files in a different directory and the directory listing feature tells the attacker the list of files/esbuild SSE endpoint: the SSE endpoint sends the URL path of the changed files when the file is changed (new EventSource('/esbuild').addEventListener('change', e => console.log(e.type, e.data)))The scenario above fetches the compiled content, but if the victim has the source map option enabled, the attacker can also get the non-compiled content by fetching the source map file.
npm inpm run watchfetch('http://127.0.0.1:8000/app.js').then(r => r.text()).then(content => console.log(content)) in a different website's dev tools.Users using the serve feature may get the source code stolen by malicious websites.