Tailwind CSS has released version 1.8.2, a minor update following closely on the heels of version 1.8.1. Both versions maintain the core philosophy of a utility-first CSS framework designed for rapid UI development. Examining their metadata reveals that the dependency trees between the two versions are identical; both share the same dependencies and devDependencies, including crucial tools like PostCSS, Autoprefixer, and various linting and testing utilities. This suggests the update likely focuses on bug fixes, performance enhancements, or minor adjustments within the existing codebase rather than introducing sweeping architectural changes or new features.
A key notable difference lies in the "dist" section, particularly the unpacked size. While both versions have the same fileCount of 195, version 1.8.2 has an unpacked size of 18858295 bytes, slightly larger than 1.8.1's 18857844 bytes. This small size increase validates the assumption that the update probably is focused on correcting issues or improving internal mechanisms. Also, the release date is different, so version 1.8.2 fixes issues encountered on the previous release. For developers, the update from 1.8.1 to 1.8.2 should be a seamless transition, guaranteeing that integration stays reliable and constant across projects because there aren't any changes to dependencies or devDependencies. We highly encourage you to update to version 1.8.2 so you have all the bug fixes and performance improvements available.
All the vulnerabilities related to the version 1.8.2 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.
