Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Configuration for rule "class-methods-use-this" is invalid
See original GitHub issueThis error just starting popping up in Atom after installing v12.0.0.
Configuration for rule "class-methods-use-this" is invalid: Value "[object Object]" has more items than allowed.
This causes an error message every time you type in Atom, and the live linter does not work.
Issue Analytics
- State:
- Created 7 years ago
- Comments:12
Top Results From Across the Web
class-methods-use-this - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >Expected 'this' to be used by class method - Stack Overflow
This is a ESlint rule, see class-methods-use-this. ... If a class method does not use this, it can sometimes be made into a...
Read more >ESlint warning - class-methods-use-this; how do I counteract ...
I'm getting this error: https://eslint.org/docs/rules/class-methods-use-this The reason is becasue I'm not using "this" in my methods.
Read more >no-invalid-this - Rules - ESLint - Pluggable JavaScript linter
The function is on an object literal. The function is assigned to a property. The function is a method/getter/setter of ES2015 Classes. (excepts...
Read more >Disallow this keywords outside of classes or class-like objects ...
Rule Details ; /*eslint no-invalid-this: "error"*/ /*eslint-env es6*/ "use strict" ; => this) ;; baz( ; function foo() ; => this) ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Nevermind, I restarted Atom and this error went away…
@ljharb That was it! My global version of eslint was at 3.4.0. After updating it to 3.6.0 and also updating my global eslint-plugins to their latest versions (eslint-plugin-import to 1.16.0, eslint-plugin-jsx-a11y to 2.2.2 and eslint-plugin-react to 6.3.0) everything is working properly with 12.0.0 in Atom. Thank you!