Autoprefixer version 9.7.3 represents a minor update over its predecessor, version 9.7.2, refining its core functionality of automatically adding vendor prefixes to CSS rules. Both versions share the same fundamental purpose: leveraging data from the "Can I Use" website to streamline CSS development and ensure cross-browser compatibility, saving developers considerable time and effort. Examining the dependencies reveals subtle but important distinctions. While both versions rely on packages like "chalk," "postcss," "num2fraction," "normalize-range," and "postcss-value-parser," the key difference lies in the versions of "browserslist" and "caniuse-lite." Autoprefixer 9.7.3 upgrades "browserslist" from version 4.7.3 to 4.8.0 and "caniuse-lite" from version 1.0.30001010 to 1.0.30001012. These updates likely reflect enhancements to browser support detection and expanded data on CSS feature compatibility, translating to more accurate and comprehensive prefixing. Furthermore, the unpacked size of version 9.7.3 is slightly larger (340531 bytes) than version 9.7.2 (340395 bytes), suggesting the inclusion of additional data or code optimizations related to the updated dependencies. Version 9.7.3 was also released on November 30, 2019, a little later compared to Version 9.7.2 that was released on November 18, 2019. By upgrading, developers benefit from improved browser support data and potentially more accurate prefixing, contributing to a more robust and consistent user experience across different browsers.
All the vulnerabilities related to the version 9.7.3 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.
