Npm is not a win32 application.

[Chris2011]

When I install the plugin under windows 7 64bit, in options I see that the plugin found my path to node.exe and to the npm package but only to the npm package and not to the npm.cmd for windows. After typing a character inside the search I got an exception that npm is not a valid win32 appliation. The problem is gone when I choose the npm.cmd file, because of I know the error for the karma thing too ;). A search for the right npm file, operation system dependent, would be nice and if someone choose the wrong file, a error message and not an exception would be better I think.

Regards

Chris

[timboudreau]

What is the path to npm.cmd on your system? I can definitely add a test for that filename when running on Windows. I don't have any Windows machines to test on, so if you'd be willing to test a patch that would be much appreciated.

[Chris2011]

Its the same as npm has. C:\Program Files\nodejs\npm.cmd. I don't know whether there is an other path for this but I think this is the main path, and sure I would be glad if I can test a patch :)

[timboudreau]

Okay, I've added npm.cmd to the list of file names to try. Download version 2.20 from my update center server here and reopen if that doesn't fix the problem.

If you want to test against a clean userdir (so it doesn't remember your previous settings), in a command shell cd into the bin/ subdirectory of wherever netbeans is installed, and run e.g.

netbeans --userdir \nbTestDir (or pick a path to a non-existent directory - you can delete it after the test)

[Chris2011]

Thx, I will test it, but an exception handling would be good too for this. Only my opinion.

[Chris2011]

it seems that all is fine now :). Thx for the patch.