Métriques du dépôt
- Stars
- (133 883 stars)
- Métriques de merge PR
- (Aucune PR mergée en 30 j)
Description
I would like to reopen #6720. I excitedly read all the thread, ending with the greatest facepalm I had in the past years.
Look, this is not a solution!
If nodejs knows how to pass these signals between processes on windows - then no reason that golang should not. No magic involved.
Full story bellow.
Mind that if the go shim is out of the loop - it works as expected, so I deduct it has to be something that golang does wrong.
I would appreciate your input on this...
What version of Go are you using (go version)?
donno. the one that nodist@0.8.7 uses
What operating system and processor architecture are you using (go env)?
Windows 10, x64
What did you do?
I'm using nodist which allows me to run different versions of nodejs side by side.
nodist uses a shim layer of go to have a look around on the env vars and local folder to detect the desired node version and call the relevant executable accordingly
See here: https://github.com/marcelklehr/nodist/issues/179
What did you expect to see?
https://github.com/marcelklehr/nodist/issues/179