-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Recommendation on Linter? #4739
Comments
This is the second time you post a comment here with this attitude. I don't think it is necessary to be so condescending. |
@vendethiel Whoa...I don't mean to be rude but really am I? I just want to see if anybody has a working linter and all of a sudden I was accused of being verbally strong... |
Turns out I misconfigured my upstream CoffeeLint package version and config...Now it works. Partially, JSX is still not working, judging from clutchski/coffeelint#619, I've also ran over some of that issue. And I won't beg for more, that's definitely precious and satisfactory to me. I'm closing this issue as I redirect my linter-of-interest to CoffeeLint. Be remember CoffeeLint v2 has only been released a week ago, so it is still broken ATM. |
I was in the same boat, so I made a fork of coffeelint that fixes the many issues. They don't seem to be accepting prs for coffeelint, so I published here: https://www.npmjs.com/package/@fellow/coffeelint2 Recommended tooling is with ESlint, using this plugin I made: https://www.npmjs.com/package/@fellow/eslint-plugin-coffee |
Since CS has been dead so long —— and so none of the CS linters (not even CoffeeLint) supported the latest features of CS2, namely JSX and import/export declaration.
The text was updated successfully, but these errors were encountered: