ESLint natively doesnt support this because this is against the spec. But if you use babel-eslint parser then inside your eslint config file you can do this: { “parser”: “babel-eslint”, “parserOptions”: { “sourceType”: “module”, “allowImportExportEverywhere”: true } } Doc ref: https://github.com/babel/babel-eslint#configuration
You need to define propTypes as a static getter if you want it inside the class declaration: static get propTypes() { return { children: PropTypes.any, onClickOut: PropTypes.func }; } If you want to define it as an object, you need to define it outside the class, like this: IxClickOut.propTypes = { children: PropTypes.any, onClickOut: PropTypes.func, … Read more
You can set the ESLint module import resolution by adding this snippet to your .eslintrc.json configuration file: { “settings”: { “import/resolver”: { “node”: { “extensions”: [“.js”, “.jsx”, “.ts”, “.tsx”] } } }, … } More informations about resolvers: https://github.com/benmosher/eslint-plugin-import#resolvers.
I don’t think hacking ESLint rules per file is a great idea. You should rather define globals in .eslintrc or package.json. For .eslintrc: “globals”: { “angular”: true } For package.json: “eslintConfig”: { “globals”: { “angular”: true } } Check https://eslint.org/docs/user-guide/configuring/language-options#specifying-globals
I have had the exact same errors when I created app using the create-react-app and setup the eslint for the application. The eslint errors were showing up in the browser rather than in the console. Once, I debugged all the dependencies. It seems that the react-scripts was causing the lint errors for me. The newest … Read more
Different lint rules for JavaScript and TypeScript files The problem happens for one of the reasons below: You’re using a rule which require type information and didn’t specify a parserOptions.project; You specified parserOptions.project, didn’t specify createDefaultProgram (it will be removed in a future version), and you’re linting files not included in the project (e.g. babel.config.js, … Read more
If you want to use experimental features (such as arrows as class methods) you need to use babel-eslint as a parser. Default parser (Espree) doesn’t support experimental features.
First, install the following module npm install –save-dev eslint-plugin-react. Then, in your .eslintrc.json, under extends, include the following plugin: ‘extends’: [ ‘plugin:react/recommended’ ] Source
You can turn off/change a particular rule for a file by putting the configurations at the top of the file. /* eslint no-use-before-define: 0 */ // –> OFF or /* eslint no-use-before-define: 2 */ // –> ON More info
Edit: as noted by Meng-Yuan Huang, this issue no longer occurs in react-scripts@^4.0.1 This error occurs because react-scripts has a direct dependency on the 2.xx range of @typescript-eslint/parser and @typescript-eslint/eslint-plugin. You can fix this by adding a resolutions field to your package.json as follows: “resolutions”: { “**/@typescript-eslint/eslint-plugin”: “^4.1.1”, “**/@typescript-eslint/parser”: “^4.1.1” } NPM users: add the … Read more