v0.22

[milesj]

No description provided.

[rotu]

I'm a little iffy on the concept of a parent bin putting any significant logic in parent bin determination. If I'm running a script with npm run, and that path contains node myscript.js, we probably need that node invocation to resolve to the same .exe as whatever magic determines the parent executable.

[milesj]

@rotu Do you have an actual example?

I tried using the shell scripts provided by npm/yarn, like bin/npm instead of bin/npm-cli.js, but they were completely broken as those scripts do a lot of weird path detection stuff, which isn't compatible with proto. So I have to execute the JS files using the parent (node).

Let's see how 0.22 works for you and if there's still any weirdness.

[rotu]

@rotu Do you have an actual example?

I don't right now since I'm not quite sure how things will work after this release. The thing I intend to try upon this release is:

$env:PATH=(Join-Path $env:PROTO_HOME "bin")
& proto run node -- --version
& proto run npm -- exec -c 'node --version'

I'm not totally sure what I expect the result to be, especially if the globally pinned node version is different from the locally pinned one!

but they were completely broken as those scripts do a lot of weird path detection stuff

Agreed. I think the shell scripts are more headache than help and I'm glad to see them go!