Created by: gimpf
When starting a react-script from a node process which is not in the path, the scripts would spawn the wrong node executable, or even fail. This can happen when starting node with an absolute path, for instance in a Bazel build.
Changes verified by both creating a new project, building and running it, and also by applying the same changes in another internal project -- this fixed our Bazel build issue.