Arcanemagus
commented
7 years ago I'm not saying it needs to sound like an evangelical street preacher, but a few tidbits about its merits would be excellent.
If you want to get more information on the differences between the two an excellent resource would be https://github.com/CSSLint/csslint/issues/668, where the authors of stylelint proposed various paths forward for merging the teams together (Like JSCS merged into ESLint), and how to get users migrated over.
Unfortunately not much came from it so many people are still stuck on CSSLint.
The primary reasons I recommend people switch over are:
- Support for modern CSS coming from being based on PostCSS instead of a custom CSS parser like CSSLint
- Support for many "CSS Like" languages such as SCSS, SugarSS, and Less built in, with more possible via plugins.
- Maintained and flexible code, it has a similar structure to ESLint allowing an ecosystem of plugins to develop around it.
Perhaps now is a good time to update the Readme with any information that might be helpful for potentially migrating/new users.
Unfortunately the bits of time that I can dedicate to these providers is mainly spent on keeping them updated and working, as I only use a few myself the readmes unfortunately fall behind as there are very few providers that have maintainers that actually work on them. Any help here would be greatly appreciated, especially since it's very hard to come at it from a "new user" perspective after writing the code that does all the work.
Does it lint on the fly or only on save?
As with any Linter provider, this can be checked from the lintsOnChange (or lintOnFly for v1 providers) property. I wouldn't expect new users (or any user) to check that though, so adding it to the readme isn't a bad idea 😉.
The owner of...
I'm actually an owner of the entire @AtomLinter organization, not "just" linter-csslint. As stated over in linter-csslint the original authors of that provider there long ago abandoned it.
The owner of the incredibly popular linter-csslint is encouraging the community to switch to this Atom package due to lack of maintenance.
Perhaps now is a good time to update the Readme with any information that might be helpful for potentially migrating/new users.
Here's a starter question: Does it lint on the fly or only on save?
I'm not saying it needs to sound like an evangelical street preacher, but a few tidbits about its merits would be excellent.