-
-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Local or Relative <linter> paths #366
Comments
What linter in specific are you using? If the SL- inherits from the |
I am using JSHint, and was previously using CSSLint, but have since dropped it. I tried searching their repo for references to NodeLinter with no luck… I will try this token thing. Thanks! |
So, I followed along in the setting tokens link that you sent, and it appears they aren't expanding properly OR i am doing it wrong… I am setting the paths in both the User settings and project settings, just in case. They are set up like: /** sublime-project file */
{
…
"SublimeLinter":
{
"paths": {
"osx": [
"${project}/node_modules/.bin/",
"${directory}/node_modules/.bin/"
]
},
}
…
}
/** SublimeLinter.sublim-settings */
{
"user":
{
…
"paths": {
"osx": [
"${directory}/node_modules/.bin/",
"${project}/node_modules/.bin/",
"/Users/thomas.bremer/.rbenv/shims/"
]
},
…
}
} but as you can see in the attachment I am getting a error message of This is the entire console log on a fresh load:
|
👍 having the same issue (eslint in my case) |
Hi, I'm having similar path issues with sublimeLinter-jshint too. In my case, ditched the ${home} and typed the full path seems to for me. Affected systems: From your console log
ST3 is not reading your path correctly. The computed paths should be spelled exactly, eg.
and not
In SublimeLinter.sublime-settings, try replacing with actual path instead of using these ${home}, ${project}, ${directory} tokens. Seems that tokens do not work in the "paths" setting. Hope this helps. |
+1 here, it boggles the mind how this wasn't implemented in sublimelinter per default. I don't want to install things globally, but project-locally. Fought about 2 hours with this, there seems no option to resolve this other than setting absolute paths, which is obviously not a solution. |
I had the same issue using eslint. I want to use eslint in my project instead of global eslint, hence all my fellow developer can uses the same eslint version and same dependencies. |
Was having the same issue as others here ( After forcing an update of all my packages and restarting Sublime I can confirm that it works as intended: SublimeLinter now uses my local I might of course have been using some ancient version of one of the packages involved. I slightly doubt it though, so I'll keep my eyes open in case it starts breaking for me again. |
@lime if you're using sublimelinter-contrib-eslint, that plugin has this functionality. sublimelinter in general, hasn't afaik |
@karolyi That is because contrib-eslint inherits from NodeLinter |
using SL3 build 3114 on windows, I seem to have come accross the same issue. I want to use phpmd linter. I installed it in a SL3 package (my package) so that it is usable by SL only. However, setting the paths in a portable way (which is important to me, as I share configs with other developers) does not work as documented. I finally managed to get it to work by doing this in SL settings: (mk1 is my package, and this is a portable installation)
when linter starts, the first setting works, which is advertised as relative to the .exe of SL itself, all this smells of bug, but I do not know enough python to fix it... |
We have been making many changes to SublimeLinter, some of which also should have fixed this particular problem. It would be really nice if you could try the beta and let us know if that fixes the problem for you. |
|
It is doable though, so you could go for it |
I was hoping to find a solution in the, but did not see one in the Issues or on the Documentation…
But, is it possible to load relative paths? Such as
./node_modules/.bin
, it'd be nice to not have to globally install linters…The text was updated successfully, but these errors were encountered: