Closed dawsbot closed 8 years ago
Tried your setup and works for me with latest XO. Try upgrading XO.
This is incorrect. The ESLint config should not be inside the xo
property. And you don't use ESLint there either, so no idea why it's there. ?
This should be simply: "test": "xo && ava"
npm uses the local binaries.
With the addition of installing eslint
as a dev dependency, this does indeed work. Thank you for the triage. Cheers 🍻
When in Sublime 3, I like to lint code with both eslint and xo (at separate times). Switching between them worked at first by first disabling one and then enabling the other. Suddenly a few weeks ago, xo no longer activates ever.
I have ensured that there are indeed xo errors (using the cli), but in Sublime none of the errors are being registered. Even upon entering the
SublimeLinter: Next Error
it shows that there are no errors.Here is the link to the repo I am currently running it with (you can clone it yourself and see since this is a link to the commit in history): https://github.com/dawsonbotsford/safpm/tree/4fce6dc05768e64704a9db9032936144fca09bfa
Here is my
SublimeLinter.sublime-settings
file contents: