Update dependency npm-check-updates to v21 #46
Reference in New Issue
Block a user
Delete Branch "renovate/npm-check-updates-21.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
^19.6.6→^21.0.0Release Notes
raineorshine/npm-check-updates (npm-check-updates)
v21.0.3Compare Source
What's Changed
Full Changelog: https://github.com/raineorshine/npm-check-updates/compare/v21.0.2...v21.0.3
v21.0.2Compare Source
What's Changed
Full Changelog: https://github.com/raineorshine/npm-check-updates/compare/v21.0.1...v21.0.2
v21.0.1Compare Source
What's Changed
Full Changelog: https://github.com/raineorshine/npm-check-updates/compare/v21.0.0...v21.0.1
v21.0.0Compare Source
⚠️ Breaking Changes
This is a major breaking change with significant architectural updates.
ESM Migration & Module System
import ncu from 'npm-check-updates'import * as ncu from 'npm-check-updates'orimport { run } from 'npm-check-updates'^20.19.0 || ^22.12.0 || >=24.0.0. This is required for nativerequire(esm)support and the Rolldown engine.>=10.0.0.Configuration Files (
.ncurc.js).ncurc.jsthat usemodule.exportswill now fail in projects that are"type": "module"..ncurc.cjsor convert them to useexport default.Dependency Updates (Pure ESM versions)
camelcase^6.3.0^9.0.0chai^4.3.10^6.2.2chai-as-promised^7.1.2^8.0.2find-up5.0.08.0.0p-map^4.0.0^7.0.4untildify^4.0.0^6.0.0Tooling & Build Changes
strip-ansiwith Node.js built-inutil.stripVTControlCharacters.vite-nodewithtsxfor TypeScript support in ESM context.Migration Guide
If you are upgrading to v21 from earlier versions:
1. Environment Check
^20.19.0 || ^22.12.0 || >=24.0.0.10.0.0.2. Update Configuration Files
If you have a
.ncurc.jsfile:Option A: Rename it to
.ncurc.cjs.Option B: Convert it to ESM:
3. Update Programmatic Usage
If you import
npm-check-updatesin your scripts:import ncu from ...toimport * as ncu from 'npm-check-updates'.Testing
Tests now use
tsxfor module loading. When running tests manually:Or use the npm script:
Related Issues & PRs
PR 1649
v20.0.2Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/raineorshine/npm-check-updates/compare/v20.0.1...v20.0.2
v20.0.1Compare Source
What's Changed
Full Changelog: https://github.com/raineorshine/npm-check-updates/compare/v20.0.0...v20.0.1
v20.0.0Compare Source
Auto Cooldown
The cooldown option is now automatically applied from the respective package manager's config:
min-release-age(#1632)npmMinimalAgeGate(excludingnpmPreapprovedPackages) (#1643)minimumReleaseAge(excludingminimumReleaseAgeExclude) (#1639)Why is this a breaking change?
Other changes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
66fb4d5c8ato94bdaec04c