Node.js default path is no longer relative to file

I'm not sure if it's an intentional feature or a regression, but recently the automatic configuration option for Node.js files is relative to the project root - not the parent directory for the file.

For example if my project root is at 

~\Documents\Development\JavaScript\example-project

and my script is: ~\Documents\Development\JavaScript\example-project\scripts\node\script1.js

The old behavior was to have the "Working directory" as: ~\Documents\Development\JavaScript\example-project\scripts\node\

and the "JavaScript file" as script1.js

Now the default is to have the "Working directory" as: ~\Documents\Development\JavaScript\example-project

and the "JavaScript file" as \scripts\node\script1.js

This can be fixed manually by editing the path, but it adds a step any time I need to run a Node script.

Is there any way to get back to the old default where "working directory" contains the full file path?

3 comments

Thanks for getting back to me Elena. Was this an intentional "feature"? Should I report as a bug or feature request in YouTrack?

My usage may not be typical, but it's pretty crippling to have to edit a setting every time I need to run a Node script.

0

Please sign in to leave a comment.