Open zzph opened 1 year ago
Well that still needs manual config as it seems. What we would like to see is completely automatic discovery/zero config. (What if you use various node versions?)
Hey, I have the same issue when using https://asdf-vm.com/ I tried with
"linters": {
"eslint": {
"env": {
"PATH": "~/.asdf/shims/node:$PATH"
},
"executable": "${folder}/node_modules/eslint/bin/eslint.js",
"selector": "source.ts, source.js - meta.attribute-with-value",
"working_dir": "${project_route:${folder:${file_path}}}"
}
}
without success.
I'm expecting the package to resolve the node version that is used within the project (hence why I tried setting working_dir
with ${folder}
thinking it would behave just like when calling node from my Terminal), or to the system's node (also manager by asdf (asdf global nodejs 21
))
Solved:
"PATH": "~/.asdf/shims/node:$PATH"
-> "PATH": "~/.asdf/shims/:$PATH"
Hi,
Just writing this as a service for others who get in this headache.
nvm
does not play nicely with eslint/sublime. I spent weeks on/off trying to configure paths etc to get this working. It just doesn't.My solution?
Remove
nvm
, instead usevolta
(seems better anyway). Thennpm install -g eslint
and voilia!My config looks like this
Maybe it's worth updating the README.MD to reflect this