On Windows, running node in the repo directory unfortunately does not use the node binary from the user's PATH, but executes ./node.js using Windows' legacy JScript engine. This is due to Windows considering .js an 'executable' extension and clearly not what we want.
We should probably also set up Windows CI to prevent bugs like these from happening in the future.
On Windows, running
nodein the repo directory unfortunately does not use thenodebinary from the user'sPATH, but executes./node.jsusing Windows' legacy JScript engine. This is due to Windows considering.jsan 'executable' extension and clearly not what we want.We should probably also set up Windows CI to prevent bugs like these from happening in the future.