Version Details and Security Vulnerabilities

📦

file-entry-cache

10.0.0

Comparision Betweeen 10.0.0 and 9.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

48.65 KB

15.82 KB

Version 10.0.0 Details

File-entry-cache version 10.0.0 represents a significant update to the popular file metadata caching library, offering improvements in performance and developer experience compared to version 9.1.0. One major change is the updated dependency on flat-cache, moving from ^5.0.0 to ^6.1.0, which likely includes bug fixes, performance enhancements, and potentially new features within the flat-cache library itself.

The development dependencies also see a major overhaul, reflecting a shift in the development workflow. Version 10.0.0 adopts modern tooling like typescript and tsup for building, indicating a commitment to type safety and optimized bundling. The testing framework is updated to vitest and @vitest/coverage-v8, replacing c8, chai, and mocha, which brings potential improvements in testing speed and code coverage reporting. The removal of webpack and glob-expand suggests a simplification of the build process, likely leveraging tsup for all bundling needs. The addition of @types/node indicates a stronger focus on TypeScript development.

The package size has also significantly increased, with the unpacked size jumping from 16KB to almost 50KB. This is an expected trade-off, as the library is much more powerful with the addition of all the new dependencies. The library is designed to optimize build processes and tools that rely on file system monitoring. The "description" field emphasizes a more lightweight caching solution. The library continues to be licensed under the MIT license and is actively maintained. Developers should note the updated dependency requirements and adjust their projects accordingly.

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.