"Unable to find executable file for node" when launch sublime from OSX Dock/Launcher

[diatech]

User will see this error if user launches sublime from OS X Dock or Launcher.

'''
Unable to find executable file for node on path list: /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:$NVM_BIN
2016-08-15 18:57:15,814: 140735267553280: ERROR: can not send request; node process not running
'''

This is because on OS X, if user launches sublime from OS X Dock or Launcher, sublime Text has its PATH set by launchctl. It will not get PATH or NVM_BIN like bashrc.

The work around here is to launch subl from a shell or hardcode the 'node_path' setting, but it could become stale.

[diatech]

Also this only happens to user who only install node via nvm and never install node "globally" i.e. "sudo npm install -g node" which will install node into /usr/local/bin/ and node in that location will be take precedence over those installed by NVM.

[zhengbli]

For OSX it is difficult to consider all the cases regarding environment setups, I would suggest just specify the node_path in your settings for now, which should be guaranteed to succeed. NVM should provide a stable environmental variable that can be used for the setting, which should work because the plugin does expand the given variable.

[burlesona]

For people who find this in the future: you can specify node_path in your ST User Settings, not specifically the typescript settings. That wasn't obvious to me from reading the above but I was able to figure it out with a bit of trial and error. It seems that a lot of packages will use this user setting if you have it set.