chore(deps): update dependency npm-check-updates to v16
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
npm-check-updates | devDependencies | major | ^14.0.1 -> ^16.0.0 |
Release Notes
raineorshine/npm-check-updates
v16.5.6
v16.5.5
v16.5.4
v16.5.3
v16.5.2
v16.5.1
v16.5.0
v16.4.3
v16.4.2
v16.4.1
v16.4.0
Feature
Added --cacheClear
option for—you guessed it—clearing the cache 🫥.
This brings the suite of cache-related options to:
-
--cache
: Cache versions to the cache file. -
--cacheClear
: Clear the default cache, or the cache file specified by --cacheFile. -
--cacheExpiration <min>
: Cache expiration in minutes (default: 10). -
--cacheFile <path>
: Filepath for the cache file (default: "~/.ncu-cache.json").
Thanks to @ly3xqhl8g9 whose code is gratefully more lucid than his username.
v16.3.25
v16.3.24
v16.3.23
v16.3.22
v16.3.21
v16.3.20
v16.3.19
v16.3.18
v16.3.17
v16.3.16
v16.3.15
v16.3.14
v16.3.13
v16.3.12
v16.3.11
v16.3.10
v16.3.9
v16.3.8
v16.3.7
v16.3.6
v16.3.5
v16.3.4
v16.3.3
v16.3.2
v16.3.1
v16.3.0
Feature
- Added workspace support!
🚢
Upgrade all workspaces:
ncu --workspaces
ncu -ws
Upgrade a single workspace:
ncu --workspace a
ncu -w a
Upgrade more than one workspace:
ncu --workspace a --workspace b
ncu -w a -w b
Upgrade all workspaces AND the root project:
ncu --workspaces --root
Upgrade a single workspace AND the root project:
ncu --workspace a --root
Notes
- If
workspaces
or--workspace
is run in--interactive
mode, ncu will prompt tonpm install
once in the root project rather than separately in each workspace (#1182). - Running
--deep
will not trigger workspace support.
v16.2.1
v16.2.0
v16.1.3
v16.1.2
v16.1.1
v16.1.0
v16.0.6
v16.0.5
v16.0.4
v16.0.3
v16.0.2
v16.0.1
v16.0.0
Breaking
- Automatic detection of package data on stdin has been removed. This feature was deprecated in
v14.0.0
. Add--stdin
for old behavior. - Wild card filters now apply to scoped packages. Previously,
ncu -f '*vite*'
would not include@vitejs/plugin-react
. Now, filters will match any part of the package name, including the scope. Use a more specific glob or regex expression for old behavior.
https://github.com/raineorshine/npm-check-updates/compare/v15.3.4...v16.0.0
v15.3.4
v15.3.3
v15.3.2
v15.3.1
v15.3.0
v15.2.6
v15.2.5
v15.2.4
v15.2.3
v15.2.2
v15.2.1
v15.2.0
v15.1.0
v15.0.5
v15.0.4
v15.0.3
v15.0.2
v15.0.1
v15.0.0
Breaking
- node >= 14.14 is now required (#1145)
- Needed to upgrade
update-notifier
with has a moderate severity vulnerability
- Needed to upgrade
- yarn autodetect has been improved (#1148)
- This is a patch, though technically it is breaking. In the obscure case where
--packageManager
is not given, there is nopackage-lock.json
in the current folder, and there is ayarn.lock
in an ancestor directory, npm-check-updates will now use yarn. - More practically, if you needed to specify
--packageManager yarn
explicitly before, you may not have to now
- This is a patch, though technically it is breaking. In the obscure case where
https://github.com/raineorshine/npm-check-updates/compare/v14.1.1...v15.0.0
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.