Tailwindcss version 1.1.2 is a minor update to the popular utility-first CSS framework, building upon the foundation of version 1.1.1. Both versions share an identical core feature set and dependency list, utilizing tools like PostCSS, Autoprefixer, Lodash, and Normalize.css to provide developers with a robust and efficient way to rapidly construct bespoke user interfaces. Key dependencies for core functionality such as bytes, chalk, and fs-extra remain consistent. The development dependencies, crucial for testing, linting, and code formatting, including Jest, ESLint, Prettier, and Babel, are also unchanged between the two versions.
The primary difference lies in the dist object: version 1.1.2 has a slightly larger unpacked size of 3,106,179 bytes compared to version 1.1.1's 3,106,139 bytes. This 40 byte difference likely represents minor bug fixes, documentation updates, or very subtle code improvements. While seemingly insignificant, these small changes can lead to increased stability and reliability for developers integrating Tailwind CSS into their projects. Developers may also observe a difference in release date, as version 1.1.2 was published on August 14, 2019, several days after version 1.1.1 on August 9, 2019. Users are advised to upgrade to 1.1.2 to leverage these subtle yet potentially impactful improvements. Remember, both version are licenced under MIT and can be found on the official repository under the Github.
All the vulnerabilities related to the version 1.1.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.
