Closed TheHedge closed 9 years ago
@TheHedge you need to file this issue with the extension author and let them know that it isn't working for you. Thanks!
Closing as problem with 3rd party extension
Appears to be a similar problem with Brackets Extensions and Yosemite.
Found this similar issue with the gulp extension. They provide a partial solution at the end of the thread of messages by creating symbolic links for node, gulp, etc.
See dalcib/brackets-gulp#1 for details.
Just marking here for others to find.
Just for the sake of people smashing their keyboards over this.
You can get the 'NodeJS integration' extension working by specifying a path to the node binary, see image.
Working for me on El Capitan.
This may be just an installation issue but I cannot find a resolution.
***\ Originally, I was only seeing this with the nodejs extension but am seeing the same issue with other extensions such as gulp.
Been using Brackets with the nodjs extension on both Win7 and Ubuntu for most of this year. Recently moved to a Macbook Pro / Yosemite and the extension can not locate the npm command and executing a command from the node.js menu returns this error.
Yet if I run the commands from other IDEs, it works as designed. Running in a terminal window, I see this.
I have tried using the Node.js configuration option to specify the path and it also does not find npm.
I am sure that this is probably a simple environment fix on the Macbook but it has be befuddled since all other IDEs and applications seem to be able to find it.
System is a Macbook Pro 15 running OS X Yosemite (10.10.1)
Thanks.