Webpack version 0.3.3 introduces notable changes compared to its predecessor, version 0.3.2, offering developers enhancements primarily in dependency management. Both versions serve as powerful CommonJs module bundlers for browsers, enabling the splitting of codebases into smaller, on-demand-loaded bundles. This feature is crucial for optimizing website loading times and improving user experience, particularly in large-scale applications. Both support for Javascript, JSON, Jade, CoffeeScript, and CSS files is out of the box, expandable with custom loaders.
However, the defining difference lies in how certain loaders are treated. In version 0.3.2, loaders like css-loader, raw-loader, jade-loader, json-loader, style-loader, coffee-loader, and script-loader were marked as optionalDependencies. Version 0.3.3 promotes these loaders to standard dependencies. This shift suggests a move towards a more integrated and streamlined experience, potentially simplifying the setup process for developers who commonly rely on these loaders. A developer upgrading from 0.3.2 to 0.3.3 should notice that those loaders that they already depended on are now installed by default.
Both versions include the same core dependencies such as esprima, sprintf, optimist, and uglify-js, and use Vows for development dependencies. These dependencies provide essential functionalities for code parsing, string formatting, command-line argument parsing, and code minification, cornerstones of the webpack's module bundling process. This stability in the core libraries means developers can expect a predictable experience across the two versions. These versions were released on the same day, only hours apart, so upgrade if you are using these old versions.
All the vulnerabilities related to the version 0.3.3 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.