You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the latest nodeclipse broke the process.env (PATH, TEMP, TMP, and SystemDrive) while debugging a nodejs process. These environment variables return "null" string literal instead of null (or undefined).
From this file, line 275 - line 278, it should check whether these java environment variables is not equals to null before adding it into the array.
Yes, indeed. I had the same issue in Maven plugin, but overlooked to fix for Node.js.
It is fixed now. You can compile sources or wait 0.12 release in the end of March
Hi,
It looks like the latest nodeclipse broke the process.env (PATH, TEMP, TMP, and SystemDrive) while debugging a nodejs process. These environment variables return "null" string literal instead of null (or undefined).
From this file, line 275 - line 278, it should check whether these java environment variables is not equals to null before adding it into the array.
https://github.com/Nodeclipse/nodeclipse-1/blob/master/org.nodeclipse.debug/src/org/nodeclipse/debug/launch/LaunchConfigurationDelegate.java#L275-278
Regards,
Patrick
The text was updated successfully, but these errors were encountered: