Gulp-size is a handy tool for Gulp-based workflows, providing developers with immediate insights into the size of their project's files. It displays the size of your project, making it an essential asset for front-end developers trying to keep the performance high in their websites and applications. This comparison explores the changes introduced between version 0.1.3 and version 0.2.0.
The core functionality remains consistent and is focused on providing a quick and easy way to measure the size of files within a Gulp pipeline. Both versions depend on gulp-util, through2, and pretty-bytes for their core functionality. However, version 0.2.0 introduces a new dependency: chalk. Chalk is used for adding color to the output in the console, increasing readability and making important information stand out at a glance. This enhances the user experience, especially in larger projects with extensive build processes.
While the core functionality for measuring file sizes stays the same, the addition of Chalk in version 0.2.0 represents a significant improvement in developer experience. The colored output can help developers quickly identify the size of individual files or groups of files, making it easier to optimize their project for performance.
Both the versions are released under the MIT license allowing developers to freely incorporate gulp-size into their open source and commercial projects.
All the vulnerabilities related to the version 0.2.0 of the package
Uncontrolled Resource Consumption in trim-newlines
@rkesters/gnuplot is an easy to use node module to draw charts using gnuplot and ps2pdf. The trim-newlines package before 3.0.1 and 4.x before 4.0.1 for Node.js has an issue related to regular expression denial-of-service (ReDoS) for the .end() method.
Command Injection in lodash
lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
