Version Details and Security Vulnerabilities

📦

sass

1.22.1

Comparision Betweeen 1.22.1 and 1.22.0

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

713.75 KB

713.74 KB

Version 1.22.1 Details

Sass version 1.22.1 represents a minor update over its predecessor, version 1.22.0, within the Dart Sass JavaScript implementation. Both versions share the core characteristic of being a pure JavaScript Sass compiler, enabling developers to integrate Sass compilation directly into their JavaScript-based workflows without external dependencies like Ruby. Key features, such as its MIT license, ensure broad usability across various project types. The author, Natalie Weizenbaum, remains consistent across versions.

The primary distinction lies in the updated dependency specification for chokidar, a file system watcher. Version 1.22.0 uses ^2.0.0, while version 1.22.1 specifies ">=2.0.0 <4.0.0". This indicates a tightening of the allowed chokidar versions. The new version explicitly limits compatibility to versions below 4.0.0, likely to address potential breaking changes or compatibility issues introduced in those later chokidar releases. Developers should be aware of this narrower chokidar version range if they rely heavily on Sass's file watching capabilities during development.

Furthermore, the unpacked size of version 1.22.1 is slightly larger (730878 bytes vs 730870 bytes in 1.22.0), suggesting minor code adjustments or dependency updates occurred. Finally, version 1.22.1 was released a couple days after the release of 1.22.0, indicating that the update brought by the new version was indeed a quick fix that followed the previous version. For most developers using Sass as a build-time tool, this subtle dependency adjustment is the most relevant factor when choosing between these versions. Consider upgrading if you have specific compatibility issues, otherwise you should be fine with both.

Security Vulnerabilities

This site is an independent open-source project and is not affiliated with, endorsed by, or sponsored by npm, Inc. or GitHub, Inc. The name “npm” is a registered trademark of npm, Inc., used here solely to describe compatibility and reference publicly available npm package data.