If i want use eslint-plugin-react-hooks, is it necessary to use standardx？

[Junting-Liu]

I want to config standard for eslint-plugin-react-hooks, but it doesn't work. So, i replace standard with standardx,like...

 "standardx": {
    "parser": "babel-eslint",
    "plugins": [
      "react-hooks"
    ]
  },
  "eslintConfig": {
    "rules": {
      "react-hooks/rules-of-hooks": "error",
      "react-hooks/exhaustive-deps": "warn"
    }
  },

But, is it the only way?
And, vscode-standardjs can't give the warning about react hook, what should i do ?

[Junting-Liu]

I think i find the reason.
It' seem like StandardJS (the vscode plugin) can't read the standardx in package.json.
Will this problem be fixed?

[jousmo]

Hello Junting
you were able to configure it ?

[Junting-Liu]

Hello Junting
you were able to configure it ?

maybe, you need to see this issue at first. It seems like a bug of vscode-standardjs and It seems can't be solved quickly。

There is my final config。 I have to use both vscode-standardjs and eslint extension in vscode，It means the real tips about hooks come from eslint。I think my config is not good，but i don't have any other better solutions right now.

  "standardx": {
    "parser": "babel-eslint",
    "plugins": [
      "react-hooks"
    ]
  },
  "eslintConfig": {
    "parser": "babel-eslint",
    "plugins": [
      "react-hooks"
    ],
    "rules": {
      "react-hooks/rules-of-hooks": "error",
      "react-hooks/exhaustive-deps": "warn"
    }
  },
  "standard": {
    "parser": "babel-eslint"
  },

[feross]

@Junting-Liu This will be fixed once we release a new version of vscode-standardjs. Sorry that this hack is required in the meantime.