eslint-plugin-jsdoc | JSDoc specific linting rules for ESLint | Code Analyzer library

I managed to resolve this by forcing the version "@typescript-eslint/eslint-plugin": "^4.17.0" - just using npm update didn't seem to work

Finally figured out a solution after visiting the NPM page for axe-cypress.

I see you've added @typescript-eslint/tslint plugin in your eslintrc file.

So seems you have tslint.json file included in your project and you'll need to add a rule to tslint.json

Issue: https://github.com/palantir/tslint/issues/3735#issuecomment-368520472

This is a conflict between the ESLint and Prettier formatting and is a well-known issue.

The solution is to let Prettier handle formatting, while ESLint takes care of code quality issues: https://prettier.io/docs/en/integrating-with-linters.html

The quickest and most comprehensive solution is this: eslint-config-prettier. What it does is, it turns off the formatting rules in ESLint, so that ESLint only takes care of code quality. And then you will have Prettier run on either on save, on a pre-commit hook (preferred), or on pre-push to reformat the codebase.

Please try adding html to eslint.additional.file.extensions list in Registry (Help > Find Action..., type registry... to locate it) and re-start the IDE

React should be putting JSX into the global namespace, so if you don't import it from anywhere then returning JSX.Element should work.

You can also import {ReactElement} from "react" and return ReactElement.

You can also import {FunctionComponent} from "react" and type the DummyWrapper function itself, not the return type, as DummyWrapper: FunctionComponent<{}>.

There's a lot of options.

But I really do not understand the use case where you would be creating an element from a static method on a class. This seems like a bad design that you should rethink. Can you make getView into a function component? Do you need the class DummyClass at all?