Rusty Key

Is `package.json` still not supported? > I'm happy to accept a PR, but we still do need to figure out what key it should look for in `package.json`. @wbyoung, what...

@ljharb doesn't `.node-version` work the same way?

I don't get it. What do you mean by "typically a single version"? To me it has exactly the same meaning as "engines" fields in packages.json — it specifies node...

Maybe the problem is that we are talking about different stuff? I am not really familiar with `nvmrc` because I am using `n`, `anv-n` and `.node-version`. > The engines field...

How are you using it? You are using narrower range or specific version in `.node-version` that is included in `engines` range? > The mental model of “engines” is simply not...

I mean, if I am specifying versions of Node which my app supports, it would be strange that I am prohibiting some of them from using in development. No?

Works fine and guaranteed to work fine are not the same. If I specify "engine", I give you some kind of guarantee that my package works with these node versions....

@Lupus, my suggestion is about providing uniformed way of sharing one option that is already configurable. I am not suggesting extending configurability of refmt

@ziyasal, 1.7.0

@ziyasal, oh, I am sorry, I looked in suggested extensions. I am using `ziyasal/vscode-open-in-github` and it is indeed 1.3.5: https://d.pr/i/8r7L53