husky post-install hook uses system node about angular-bazel-example

[alexeagle]

Hmm, since husky runs outside of the build context, I'm not sure what to do about this. There are plenty of non-build-related tools that expect to have node installed.
Probably the right thing is just to make this non-fatal.

[alexeagle]

Note, have the same problem in angular/angular which has a preinstall hook to ensure you're using npm and not yarn. @gkalpak usually has clever ideas about manipulating this.

[gkalpak]

I can't think of a clean way to handle this (other than ensuring that the executables you reference in your npm scripts are globally available) 😕

[alexeagle]

--scripts-prepend-node-path seems like the right answer, and I confirmed it works for projects that use npm.
Also it is in yarn/cli.js - but it seems broken, when I try it I don't see any effect. Needs more debugging...

[gregmagolan]

This should be fixed now as the PATH to the bazel managed is set when a node process is started under Bazel