Version Details and Security Vulnerabilities

📦

sass-loader

13.0.0

Comparision Betweeen 13.0.0 and 12.6.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

56.22 KB

84.74 KB

Version 13.0.0 Details

Sass-loader 13.0.0 brings several updates compared to the previous stable version 12.6.0, primarily focusing on dependency upgrades and alignment with newer tooling standards. For developers, this means potential compatibility improvements and access to the latest features of related packages. The core dependencies of klona and neo-async remain consistent between the versions, ensuring core functionality isn't dramatically altered. The significant changes are within the devDependencies, which are important for development workflows and testing. Key updates include upgrades to jest (from 27.5.0 to 28.1.0), sass (from 1.49.7 to 1.51.0), eslint (from 8.8.0 to 8.15.0), webpack (from 5.68.0 to 5.72.1), @babel/cli (from 7.17.0 to 7.17.10), @babel/core (from 7.17.0 to 7.17.10), @commitlint/cli (from 16.2.1 to 17.0.0), @babel/preset-env (from 7.16.11 to 7.17.10) and jest-environment-node-single-context (from 27.2.0 to 28.0.0).

These upgraded development dependencies typically bring performance improvements, bug fixes, better support for modern JavaScript/Sass features, and enhanced linting/testing capabilities. This leads to a more robust development environment and potentially reduces integration issues when incorporating sass-loader into larger projects. While peerDependencies remain the same, ensuring compatibility with existing Sass, Fibers, and Webpack setups as before, the upgraded sass and webpack versions in devDependencies suggest a focus on supporting the newest features available in these core tools. It's recommended developers review the changelogs for each upgraded dev dependency to determine the specific impact on their workflow.

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.