eslint

Object.hasOwnProperty() yields the ESLint ‘no-prototype-builtins’ error: how to fix?

by

You can access it via Object.prototype: Object.prototype.hasOwnProperty.call(obj, prop); That should be safer, because Not all objects inherit from Object.prototype Even for objects which inherit from Object.prototype, the hasOwnProperty method could be shadowed by something else. Of course, the code above assumes that The global Object has not been shadowed or redefined The native Object.prototype.hasOwnProperty has … Read more

Parsing error: Cannot read file ‘…/tsconfig.json’.eslint

by

By default, the projects (in parserOptions) are resolved relative to the current working directory. If you run eslint in a different working directory to the folder containing tsconfig.json, @typescript-eslint/parser will not be able to locate the file. To fix this, you can set tsconfigRootDir to __dirname, which would make the parser resolve the project configuration … Read more

TSLint extension throwing errors in my Angular application running in Visual Studio Code

by

Like Tuấn Nguyễn described, you need to: Go to the Command Palette by pressing Ctrl + Shift + P, In the input that pops up at the top of the Visual Studio Code, start typing TSLint: Manage workspace library execution” and hit the Enter key. From the menu that replaces the input, pick enable workspace … Read more

“parserOptions.project” has been set for @typescript-eslint/parser

by

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

ESLint Parsing error: Unexpected token

by

Unexpected token errors in ESLint parsing occur due to incompatibility between your development environment and ESLint’s current parsing capabilities with the ongoing changes with JavaScripts ES6~7. Adding the “parserOptions” property to your .eslintrc is no longer enough for particular situations, such as using static contextTypes = { … } /* react */ in ES6 classes … Read more

Expected linebreaks to be ‘LF’ but found ‘CRLF’ linebreak-style

by

Check if you have the linebreak-style rule configure as below either in your .eslintrc or in source code: /*eslint linebreak-style: [“error”, “unix”]*/ Since you’re working on Windows, you may want to use this rule instead: /*eslint linebreak-style: [“error”, “windows”]*/ Refer to the documentation of linebreak-style: When developing with a lot of people all having different … Read more

Disable eslint rules for folder

by

To ignore some folder from eslint rules we could create the file .eslintignore in root directory and add there the path to the folder we want omit (the same way as for .gitignore). Here is the example from the ESLint docs on Ignoring Files and Directories: # path/to/project/root/.eslintignore # /node_modules/* and /bower_components/* in the project … Read more

eslint: error Parsing error: The keyword ‘const’ is reserved

by

ESLint defaults to ES5 syntax-checking. You’ll want to override to the latest well-supported version of JavaScript. Try adding a .eslintrc.json file to your project. Inside it: { “parserOptions”: { “ecmaVersion”: “latest” }, “env”: { “es6”: true } } Hopefully this helps. EDIT: I also found this example .eslintrc.json which might help.

Hata!: SQLSTATE[HY000] [1045] Access denied for user 'divattrend_liink'@'localhost' (using password: YES)