Vasyl Boroviak

Alternatively, it's not necessary to use "engines" property. We can have our own "nvmrc" property in package.json. The `package.json` can have a special field called `"nvmrc"` which would contain the...

1. Nope. No need for JSON parser. See my POC above. 2. Why people want to put `.nvmrc` to `package.json`? There are answers above in this thread. My personal use...

@ljharb good job spotting the "space problem" in my POC. You are good with RegEx. 👍 So you probably know that this `grep -o '"version":\s*"[^"]*' package.json | grep -o '[^"]*$'...

Mate, not 99%. I said 99.9999%. Please, avoid faking other people words. It's unproductive. Thanks.

Good news everyone! There is a JSON parser written in pure shell script. https://github.com/dominictarr/JSON.sh Here is how I can extract any value from a JSON file: ```sh cat package.json |...

I do not understand the arguments "complexity of parsing JSON" and "JSON parsing in posix would be a very complex". The complexity is near 0 since there is a robust...

I understand the implementation time cost. JSON.sh had no updates in 5 years. Not sure what to maintain there. I foresee 0 maintenance effort there. So I don't understand the...

About JSON parsers. I invite everyone to read this issue starting from the comment: https://github.com/nvm-sh/nvm/issues/651#issuecomment-701360709 In other words, there is a robust JSON.sh parser written in shell (180 lines of...

> But, well, the proposed parser doesn't fulfill criteria of nvm. It just doesn't work on all target platforms. I think we discussed that already. We came to conclusion that...

I propose this in `package.json`. I.e. avoid using existing "engines" property: ```js { // ... "nvm": "16" // ... } ```