Autoprefixer 9.7.1 is a minor version update to the popular CSS vendor prefixer, building upon version 9.7.0. Both versions, designed to parse CSS and automatically add vendor prefixes based on data from the "Can I Use" website, aim to streamline the development workflow by ensuring compatibility across different browsers. The core functionalities and general usage remain consistent between the two versions, focusing on easing cross-browser compatibility.
A key difference lies in their dependencies. Autoprefixer 9.7.1 upgrades its dependency on caniuse-lite to version ^1.0.30001006 from ^1.0.30001004 in version 9.7.0. This update to caniuse-lite, which provides data on browser support for CSS features, likely incorporates the newest browser versions and CSS features, allowing Autoprefixer to prefix accurately. The postcss dependency also sees an update, moving from version ^7.0.19 to ^7.0.21, likely including bug fixes and minor feature enhancements within the PostCSS ecosystem that Autoprefixer relies on.
Developers upgrading to 9.7.1 can expect improved accuracy in prefixing for newer CSS features and browser versions, stemming from the caniuse-lite data update. Project size may vary slightly, with version 9.7.1 unpacking to 337286 bytes compared to 9.7.0's 336512 bytes, in part thanks to the newer caniuse-lite version. The release dates indicate rapid iteration, with 9.7.1 arriving approximately a week after 9.7.0, signifying the project's active maintenance and commitment to staying current with the evolving front-end landscape.
All the vulnerabilities related to the version 9.7.1 of the package
PostCSS line return parsing error
An issue was discovered in PostCSS before 8.4.31. It affects linters using PostCSS to parse external Cascading Style Sheets (CSS). There may be \r discrepancies, as demonstrated by @font-face{ font:(\r/*);} in a rule.
This vulnerability affects linters using PostCSS to parse external untrusted CSS. An attacker can prepare CSS in such a way that it will contains parts parsed by PostCSS as a CSS comment. After processing by PostCSS, it will be included in the PostCSS output in CSS nodes (rules, properties) despite being originally included in a comment.
