Closed arlodesign closed 5 years ago
Also confirmed that /Users/myuser/.nvm/versions/node/v6.5.0/bin
is in my $PATH
@arlodesign
Trying adding this to your CSSComb config:
{
"node-path": ":/Users/myuser/.nvm/versions/node/v6.5.0/bin"
}
(note the colon before /Users
)
Worked for me, installing Node with NVM.
@joeczucha I don't know but i think you are using osx maybe? I've looked into the python code, and I think the above mentioned node-path setting is only used if you are on a mac. I didn't dig myself into the real problem here but the subprocess.Popen method wich is used to call node does not use the $PATH variable. So i've just hard coded the path into the method call in CSScomb.py at line 43.
p = Popen([self.get_node_path() + 'node', COMB_PATH] + [syntax, config, folder],
stdout=PIPE, stdin=PIPE, stderr=PIPE,
env=self.get_env(), shell=self.is_windows())
In this case you may want to include a slash at the end of the path. Now it is working for me at least.
This appears to be resolved.
Mac OS X El Capitan 10.11.6 Sublime Text 3, Build 3114 Node v6.5.0, installed via nvm (though I haven't gotten any version of node to work)
I know a lot of folks have posted issues concerned with using this package with node installed via nvm. I've now tried both updating the sublime settings, both user and package level, as well as symlinking
/usr/local/bin/node
to the latest version. No such luck.I've installed CSScomb globally:
Contents of
~/Library/Application Support/Sublime Text 3/Packages/User/CSScomb.sublime-settings
I've tried it with and without the
:
at the beginning. I've tried setting this value in~/Library/Application Support/Sublime Text 3/Packages/CSScomb/CSScomb.sublime-settings
, as well.My symlink
The error I get in the Sublime console every time I try to run CSScomb
…which, of course, provides this:
What I've tried
And I know Sublime is having no trouble finding node…
SublimeLinter is still working fine. I'm using SublimeLinter-contrib-eslint (which uses the setting
node_path
with an underscore), and it's working just fine pointing at Node v6.5.Any help you can provide is greatly appreciated. Thank you.