PostCSS version 8.3.8 is a minor update to the popular CSS transformation tool, building upon the foundation laid by version 8.3.7. Both versions, sporting the same core functionality of transforming styles using JavaScript plugins, share the same fundamental dependencies: nanoid for generating unique IDs and source-map-js for robust source map handling, crucial for debugging CSS in complex projects.
The primary difference lies in a dependency update. Version 8.3.8 upgrades the nanocolors dependency from version 0.1.5 to version 0.2.2. While seemingly small, this update likely includes bug fixes, performance improvements, and potentially new features within the nanocolors library, which handles terminal styling. This is relevant for developers building PostCSS plugins that output colored messages to the console.
For developers choosing between these versions, the upgrade to 8.3.8 is generally recommended. It includes the latest improvements and potential security patches within the nanocolors dependency. Given the shared core dependencies and feature set, upgrading should be seamless for most users. Both versions provide a well-established and reliable platform for modern CSS workflows, enabling automation, linting, and advanced CSS features through a rich ecosystem of plugins. PostCSS remains a vital tool for any front-end developer seeking greater control and flexibility over their styling process.
All the vulnerabilities related to the version 8.3.8 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.
