chore(deps): update dependency installed-check to v9
This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| installed-check | ^3.0.0 -> ^9.0.0 |
Release Notes
voxpelli/node-installed-check (installed-check)
v9.3.0
v9.2.0
- Add
--workspace-ignoreto enable ignoring paths when looking up workspaces (#91, #93)a1834c5 - Fix incorrect flag alias in README (#92)
74cf007Thanks @jfmengels 🙏
v9.1.2
- temporarily readd the deprecated
--engine-ignore/--engine-no-devflags, to ease transitionea00dd9
v9.1.1
Update installed-check-core to 8.2.2, containing these fixes:
- do not fail on pnpm
workspace:version range (01ff126) - ignore
@types/*packages in engine check (f87823e) - latest
list-installed, supports symlinks (3c432bf)
v9.1.0
- In verbose mode: Output workspace success summary
66bb6a2 - Update
installed-check-coreto supportpnpmda770ca - Update dev dependencies
bc8818e
v9.0.0
Based on [email protected] which adds:
- Support for workspaces (#31)
- Verification of peer dependency ranges (#10)
- Support for glob batters in ignores (#41)
- Improved presentation with suggestions being presented separately
Breaking changes:
- Requires Node.js
>=18.6.0 - Defaults to check all workspace packages in addition to the existing check of the (workspace) root
- Defaults to verify peer dependency ranges
-
--engine-ignoreand--engine-no-devhas been renamed to--ignoreand--ignore-devand is also used by peer dependency check -
--strictis now implemented withininstalled-check-coreinstead, which allows for some warnings to stay as warnings when --strict is set - Output has changed, but if output is parsed, instead use `installed-check-core directly or open an issue requesting a machine readable output
v8.0.1
- Update dependencies
8e1137a
v8.0.0
- SEMI-BREAKING: Require Node
>=16.10.0(follows sindresorhus/meow#235)12d6219
v7.1.2
- Update
installed-check-core52d28d9
v7.1.1
- Update
installed-check-coreb4dae70
v7.1.0
- Feature/fix: Handle aliased packages #42
b022cb0 - Internal: Replace dependency-check with knip
5c69958
v7.0.0
v6.0.5
- Update dependencies
v6.0.4
-
Dependencies: Update
installed-check-core
v6.0.3
- Fix regression on Windows
72fe7b4
v6.0.2
- Mark as a ESM module
2e934a7 - Use extracted
version-guardmodule13b6047 - ...and some GitHub Actions updates
v6.0.1
- Update dependencies, including new
installed-check-core3ca2d49 - Update dev dependencies
826cb3906f25d4f164d4a - Use
npm-run-all2f755fe1
v6.0.0
-
Breaking change: Now requires Node.js version matching ^14.18.0 || >=16.0.0
, to match that of[email protected]` - Internal: Now an ESM based project
v5.0.0
-
Breaking change: Now requires Node.js version matching
^12.20.0 || ^14.13.1 || >=16.0.0, to match that of[email protected]which in turn sets it to ensure compatibility with ESM-based dependencies -
Possibly breaking change: Uses new
5.xversion ofinstalled-check-core, which contains a newer engine intersection module as well as some alterations to errors, warnings and notices to make them more robust and consistent (thanks to eg. new tests)
v4.0.0
- Breaking change: Now requires at least Node.js 12.x (somewhat following the LTS of Node.js itself)
-
Dependencies: Moved from
2.xto modern4.xversion ofchalk -
Dependencies: Now using
meowinstead ofdashdashto parse the CLI input -
Dependencies: Uses new
4.xversion ofinstalled-check-core, containing fewer dependencies that are more modern and eg. typed and async in themselves - Internal: Added strict type checking (using Typescript) verifying that the javascript code doesn't violate any assumptions.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.