Webpack version 0.3.12 arrived shortly after v0.3.11, both iterations of this early stage bundling tool are designed to package CommonJS modules for browser deployment, enabling developers to split their codebases into smaller, on-demand loaded bundles, enhancing initial load times and overall application performance—a significant advantage in web development. Both versions boast inherent support for a variety of file types, including JavaScript, JSON, Jade (now Pug), CoffeeScript, and CSS. Moreover, they are extensible with custom loaders to accommodate additional file formats, offering developers considerable flexibility in managing diverse project structures.
Examining the dependency lists reveals no apparent changes between the two versions. Both rely on the same set of core tools: Esprima for JavaScript parsing, sprintf for string formatting, Optimist for command-line argument parsing, UglifyJS for JavaScript minification, and a suite of loaders for processing CSS, raw text, Jade templates, JSON files, LESS stylesheets, inline styles, CoffeeScript files, and generic scripts. Developers will appreciate the consistent tooling available in both versions.
The key difference is the release date; version 0.3.12 was released just hours after its predecessor. This suggests the changes from the previous version were non-breaking. Given the absence of modified dependencies or features, this update likely involved minor bug fixes, internal tweaks, or documentation improvements. If you're using either version, you're equipped with the core Webpack capabilities from that era, but consider migrating to a later version to leverage modern features and performance enhancements.
All the vulnerabilities related to the version 0.3.12 of the package
Incorrect Handling of Non-Boolean Comparisons During Minification in uglify-js
Versions of uglify-js prior to 2.4.24 are affected by a vulnerability which may cause crafted JavaScript to have altered functionality after minification.
Upgrade UglifyJS to version >= 2.4.24.
Regular Expression Denial of Service in uglify-js
Versions of uglify-js prior to 2.6.0 are affected by a regular expression denial of service vulnerability when malicious inputs are passed into the parse() method.
var u = require('uglify-js');
var genstr = function (len, chr) {
var result = "";
for (i=0; i<=len; i++) {
result = result + chr;
}
return result;
}
u.parse("var a = " + genstr(process.argv[2], "1") + ".1ee7;");
$ time node test.js 10000
real 0m1.091s
user 0m1.047s
sys 0m0.039s
$ time node test.js 80000
real 0m6.486s
user 0m6.229s
sys 0m0.094s
Update to version 2.6.0 or later.
Regular Expression Denial of Service in clean-css
Version of clean-css prior to 4.1.11 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.
Upgrade to version 4.1.11 or higher.
Sandbox Bypass Leading to Arbitrary Code Execution in constantinople
Versions of constantinople prior to 3.1.1 are vulnerable to a sandbox bypass which can lead to arbitrary code execution.
Update to version 3.1.1 or later.