I have a functional workflow that I'm looking to enhance. Currently, I am developing a JavaScript library and conducting smoke tests on the code by using webpack to bundle the library and save it to a file that can be included in an HTML file for testing purposes.
My current process involves making changes to the file in Eclipse, saving it, then switching over to Terminal to run "npm run buildInbrowser" which triggers "webpack --config inbrowser.config.js".
While the configuration works smoothly with webpack, npm setup, and running the commands in Terminal, I encounter an error when attempting to configure Eclipse to execute the same commands - "env: node: No such file or directory". Attached are screenshots of my NPM launch configurations for reference.
For context, I am using MacOSX Catalina with Nodeclipse, npm version 9.3.1, and Node version 16.18.0. Despite being able to run the commands flawlessly in Terminal, there seems to be an issue when attempting to do so through Node. It appears like there might be a simple oversight on my part causing this discrepancy.
https://i.stack.imgur.com/qrkwy.png