0
0
mirror of https://github.com/tj/n.git synced 2024-11-21 18:48:57 +01:00

Add use of jq to README and CHANGELOG

This commit is contained in:
John Gee 2024-08-16 16:37:02 +12:00
parent acf6b5c639
commit 273a485c9e
2 changed files with 6 additions and 1 deletions

View File

@ -9,6 +9,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased] (date goes here)
### Changed
- if `jq` is available, use `jq` for reading `engines` from `package.json` instead of using `node` ([#810])
## [9.2.3] (2024-04-21)
### Fixed
@ -506,6 +510,7 @@ Only minor functional changes, but technically could break scripts relying on sp
[#746]: https://github.com/tj/n/pull/746
[#764]: https://github.com/tj/n/pull/764
[#785]: https://github.com/tj/n/pull/785
[#810]: https://github.com/tj/n/pull/810
<!-- reference links for releases -->

View File

@ -143,7 +143,7 @@ There is an `auto` label to read the target version from a file in the current d
- `.nvmrc`: version on single line. Used by `nvm`.
- if no version file found, look for `engine` as below.
The `engine` label looks for a `package.json` file and reads the `engines` field to determine compatible Node.js. Requires an installed version of `node`, and uses `npx semver` to resolve complex ranges.
The `engine` label looks for a `package.json` file and reads the `engines` field to determine compatible Node.js. Requires an installed version of `jq` or `node`, and uses `npx semver` to resolve complex ranges.
There is support for the named release streams: