Tailwind CSS saw a notable update with the release of version 1.8.0, building upon the foundations laid by version 1.7.6. Both versions share the same core mission: to provide a utility-first CSS framework for rapid UI development. Developers familiar with version 1.7.6 will find the upgrade to 1.8.0 a relatively smooth transition, as the fundamental approach and dependency structure remain consistent. However, there are key improvements and additions worth noting.
One significant difference lies in the package size. Version 1.8.0 has a larger unpacked size (18856833 bytes) and file count (195) compared to version 1.7.6 (14876760 bytes and 187 files respectively). This suggests the inclusion of new features, assets, or optimizations in the newer version. The dependency lists are nearly identical, indicating that the core underlying tools haven't changed drastically; the updates likely center on enhancements within the Tailwind CSS framework itself. Developers should be aware of the increased size, potentially impacting build times or bundle sizes depending on their project setup.
While the specifics of what constitutes the added size are not explicitly detailed, users can expect tweaks to existing utilities, potential bug fixes, and possibly the introduction of new utility classes or configuration options. For those regularly using Tailwind CSS, upgrading to version 1.8.0 is generally recommended to benefit from the latest improvements and ensure compatibility with evolving web development standards. The release date also gives a temporal reference about how recent and updated the library is.
All the vulnerabilities related to the version 1.8.0 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.
