Version Details and Security Vulnerabilities

📦

unplugin-auto-import

19.1.1

Comparision Betweeen 19.1.1 and 19.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

106.05 KB

105.87 KB

Version 19.1.1 Details

Unplugin-auto-import has released a new version, 19.1.1, following closely on the heels of version 19.1.0. While both versions maintain the core function of registering global imports on demand for Vite and Webpack, subtle differences might influence development workflows.

A key dependency update is observed in unimport, moving from version 4.1.1 to 4.1.2. This suggests potential bug fixes or minor feature enhancements within the unimport library that could impact how modules are handled by unplugin-auto-import. The unplugin-auto-import core library itself has an increment in the unpacked size after installation, being 108593 KB compared to the older version that was 108408 KB.

Several development dependencies have also seen updates. Notably, eslint moved from 9.20.1 to 9.21.0, potentially introducing new linting rules or performance improvements. @antfu/eslint-config also jumps from 4.2.0 to 4.3.0, potentially affecting the code style enforced during development. Other updated dev dependencies include @types/node, @antfu/utils, @vueuse/metadata, vite, rollup, vitest, and tsup. These upgrades likely bring performance gain, bug fixes, enhanced type definitions, and improved build processes.

The releaseDate is important in observing how recent the changes are, in the new version of 19.1.1 is 2025-02-27T03:26:04.761Z while the older 19.1.0 is 2025-02-15T08:34:36.499Z.

Developers leveraging unplugin-auto-import will find these changes incrementally beneficial, especially those relying on the latest features and fixes incorporated into its dependencies. Consider upgrading to 19.1.1 to take advantage of these improvements.

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.