A note to people using this package

[Darkle]

Hi, since this package hasn't been updated in a while, I just thought I'd mention that it's possible to use eslint_d with the regular https://github.com/SublimeLinter/SublimeLinter-eslint package.

If you install https://github.com/SublimeLinter/SublimeLinter-eslint, open the Sublime Linter settings, then in the section for eslint, add the executable setting and point it to the eslint_d binary: http://www.sublimelinter.com/en/stable/linter_settings.html#executable

[jeremytm]

This is now the only workaround when running alongside the latest SublimeLinter release (4.12) which brings recent deprecations into full force, and breaks this package completely.

[trongthanh]

Many thanks. I just saw the errors in ST3 console and come here to report the issue and found this helpful note. Switch to the defacto SublimeLinter-eslint is the better way in the long run, IMO.

[gillibrand]

I don't see an existing section for "eslint" when I open the settings. So in the right-side "user settings" file I added just the path as seen below. This is on Windows. I assume this gets merged on top of some default settings. Just using the eslint_d command name alone didn't work even though it's in my PATH.

"linters": {
	"eslint": {
		"executable": "c:\\Users\\MY_USER_NAME\\AppData\\Roaming\\npm\\eslint_d.cmd"
	}

[juan-restrepo]

Last night I must have some sort of autoupdate and my linter was broken. Thank you for posting this!

[kaste]

The latest version of SublimeLinter-eslint automatically detects eslint_d; no manual configuration should be necessary anymore.