Autoprefixer is a powerful PostCSS plugin that automatically adds vendor prefixes to CSS rules, ensuring cross-browser compatibility and saving developers valuable time and effort. Comparing versions 9.8.3 and 9.8.2 reveals subtle but important differences for those relying on this tool. Both versions share the same core functionality: parsing CSS and applying prefixes based on data from "Can I Use," a comprehensive resource detailing browser support for web technologies.
Key dependencies like kleur, postcss, browserslist, num2fraction, normalize-range, and postcss-value-parser remain consistent, indicating that the underlying CSS processing and value manipulation logic remained stable between the two versions. The caniuse-lite dependency which dictates, which browser versions are supported, saw a significant update, progressing from version 1.0.30001084 in 9.8.2 to 1.0.30001087 in 9.8.3. This indicates enhanced and more current browser support information, an important consideration for developers targeting a wide array of browsers. The unpacked size increased slightly from 348870 to 348964, reflecting the additions to caniuse-lite.
Ultimately, upgrading from 9.8.2 to 9.8.3 provides the crucial benefit of enhanced accuracy in prefixing due to the updated caniuse-lite data. Developers adopting or already using Autoprefixer should prioritize staying current with minor version updates like this to benefit from the most accurate and up-to-date browser support information. This ensures the generated CSS is relevant and optimized for the prevailing browser landscape, leading to improved user experiences across different platforms.
All the vulnerabilities related to the version 9.8.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.
