Tailwind CSS version 1.0.5 represents a subtle but noteworthy iteration over its predecessor, version 1.0.4, offering refinements that cater to developers seeking a utility-first CSS framework. Both versions share the same core dependencies, including essential packages like postcss, lodash, and autoprefixer, which form the foundation for Tailwind's functionality. The development dependencies showcase more prominent changes, impacting the tooling and linting setup.
While version 1.0.4 utilizes ESLint version 5.15.1 and eslint-config-prettier version 4.1.0, version 1.0.5 upgrades ESLint to version 6.0.1 and eslint-config-prettier to version 6.0.0. This indicates an evolution in the project's code quality and style enforcement practices, potentially incorporating new linting rules and formatting standards. Besides that we can see that the "fileCount" in the "dist" for version 1.0.5 is 137, where for the previous version is 138, also the unpacked size is a bit lower, 2162515 vs 2319970. This latest version was released more recently, on July 11, 2019, compared to version 1.0.4 released on June 11, 2019. For developers using Tailwind CSS, these changes signify an improved and more consistent development experience with the newest dependecies, particularly concerning code linting and potential performance improvements that comes with the file count reduce. Although the core functionalities remain consistent, the updated tooling suggests a commitment to code quality and modern development workflows, making version 1.0.5 a worthwhile upgrade.
All the vulnerabilities related to the version 1.0.5 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.
