Definition for rule 'react/jsx-no-duplicate-props' was not found - error on lint about semistandard HOT 17 CLOSED

+1 I ran into this issue as well and it is rather annoying that your linter wrongly tells you something is wrong when it isn't - I am not doing React yet get Definition for rule 'react/jsx-no-duplicate-props' was not found

from semistandard.

Same issue. I'm using linter-js-standard plugin of Atom.

[email protected]
[email protected]
[email protected] + [email protected]

Updating to 7.0.3 fixes the issue! See #37.

from semistandard.

I'm also seeing this, but only after upgrading to node 4.2 & npm v3.

npm --version
3.4.0

node --version
v.4.2.2

npm ls eslint-plugin-react
...
└─┬ [email protected]
  └── [email protected]

from semistandard.

Hm.. strange.
My current versions. It is in my Docker container, but in my host is node 5 and npm 3.3.9.

node -v                                                                                                                                                                                                 
v4.1.2
npm --version
3.3.6

from semistandard.

Is there a solution for this yet? I just switched to Atom and installed linter-js-standard, but Definition for rule 'react/jsx-no-duplicate-props' was not found shows up on every file. I typically use Sublime with JSHint, so I'm not sure what to do. I read #37 and tried some basic troubleshooting (reinstalling, ensuring everything's up to date, etcetera), but nothing seems to work.

from semistandard.

@merktassel I don't know if there's a solution. I've just switched to Atom too.
I'm using semistandard with Eslint (linter-eslint) and this config file: Flet/eslint-config-semistandard

from semistandard.

Hmm, I'll have to try that package instead. I've been using linter-js-standard with the semistandard style.

from semistandard.

@merktassel, a solution is a one-character change as in #72 but considering the solution has been there waiting for more than 4 months, you are right in moving away from this package. It's a shame.

from semistandard.

Darn. Is this problem strictly related to the linter-js-standard plugin, or the eslint-config-semistandard config as a whole? I'm loving Atom so far, but it's really annoying that semistandard won't work properly.

from semistandard.

Sorry, folks, we've just updated semistandard and its deps. Can someone give the latest a try?

from semistandard.

Not working yet with atom using linter-js-standard. I've been using eslint-config-semistandard and it's working fine.

node -v
v6.1.0
npm -v
3.8.9

from semistandard.

@lubien I wouldn't jump to conclusions so fast, you're testing this issue with linter-js-standard and should have tested with semistandard instead. And I would recommend to check if you have updated semistandard under your projects

from semistandard.

@ricardofbarros I'm not jumping.

{
  "devDependencies": {
    "babel-eslint": "^6.0.4",
    "semistandard": "^8.0.0"
  },
  "semistandard": {
    "parser": "babel-eslint"
  }
}

It's just strange. Using semistandard seems ok, but the linter outputs the error.

from semistandard.

So @Flet release is okay and the problem isn't on semistandard but on linter-js-standard. I just said that because you could have induced @Flet in error. Mind if I ask you what is the linter-js-standard version ?

from semistandard.

I apologize since it sounded like that. Version 3.3.2 of linter-js-standard, I've installed today to test it.

from semistandard.

@Flet I cross-referenced this issue back to linter-js-standard. As it seems, the problem is on linter-js-standard and not on semistandard. So I think you can close this.

from semistandard.

Thanks @ricardofbarros

from semistandard.