Consider adding ESLintBear

[attila0x2A]

Current linters don't catch a lot of issues in the code, so it may be beneficial to add ESLintBear or tweak configuration of existing ones to make PRs less painful and improve code quality in general.

[gitmate-bot]

Thanks for reporting this issue!

@coala-analyzer/coala-contributors, your aid is required, fellow coalaian. Help us triage and solving this issue!

[KVGarg]

Hi @Uran198 👋 Is this issue still needs to be solved, because over the period of 2 years many new Bears have been developed that parses our code that result in warnings, So wanted to know whether is this issue still need to be solved or not?
I would love to take this issue, if it needs to be solved 😇 just need some information what needs to be done

[attila0x2A]

Sorry, but I am not sure about it. I haven't worked on this for a long time. From coala-html/.coafile it seems there were not so many bears added for js linting. I think all I wanted back there is more linting support for JS files. So if you want to do it, you'll need to tweak coala configuration.
Or maybe JSHint already provides the necessary amount of linting. Start with checking that and close this issue if you think that it is sufficient.
Unfortunately, I am not the right person to send Pull Requests to if something still needs to be done. I have lost all the context and did not keep track of the changes to this project.
The good place to get started would probably be https://github.com/coala/coala-html#getting-involved