Hey @davebowker - been a while since I’ve used Atom, but I would probably use the base linter package for the core functionality, and then add language-specific support with linter-eslint, linter-stylelint, and linter-php.
linter-eslint and linter-stylelint are just interfaces for ESLint and Stylelint, respectively, which means you can pretty much configure those linters the same way you would without Atom being in the picture.
Sage places its Stylelint config in package.json and its ESlint config in .eslintrc.js. If you want to customize those, that’s where I would do it. Those are both standard locations and should work out of the box with the above plugins.
For general info on using Stylelint and ESLInt:
For linter-php to work you need to have PHP installed and you may need to tell Atom where to find it if it can’t detect it in your paths. Once it can find PHP, I think that’s all it needs in order to work.
@mmirus Thanks! That’s fantastic. I had a couple of linter plugins installed but each kept on asking for a config that wasn’t included with Sage! That plugin though seems to pick up some of the errors I was running into when building for production. Many thanks!