Version Details and Security Vulnerabilities

📦

call-matcher

2.0.0

Comparision Betweeen 2.0.0 and 1.1.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

15.89 KB

114.09 KB

Version 2.0.0 Details

Call-matcher version 2.0.0 presents several notable updates compared to its predecessor, version 1.1.0, affecting both its dependencies and development tools. A key change is the removal of core-js as a direct dependency, suggesting potential adjustments in how the library handles ECMAScript compatibility or a shift to relying on native implementations. On the other hand, espurify was updated to version 2.0.0 from 1.6.0, potentially introducing enhancements in AST (Abstract Syntax Tree) purification and security.

Significant modifications appear in the development dependencies. Version 2.0.0 eliminates browserify, derequire, dereserve, jshint, licensify, and package-json-filterify, while introducing semistandard and snazzy. This indicates a shift toward a standardized code style enforced by semistandard and potentially cleaner, more visually appealing output with snazzy, likely targeting improved code quality and maintainability. The core functionality of matching ECMAScript CallExpressions based on function/method signatures, remains the library's primary focus, empowering developers to analyze and manipulate JavaScript code structures effectively. The library is MIT licensed and the source code is available on Github. The updated espurify and the tooling changes contribute to a more modern and streamlined development workflow. Developers should consider these dependency adjustments when upgrading and evaluate potential impacts on their projects, especially concerning ECMAScript compatibility if they relied on core-js.

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.