react-hooks | 🎣 ⚛ | Frontend Utils library

I got two different solution.

1. remove

So the problem is, ESLint detects by default current working directory as the root folder. So this led ESLint to detect root tsconfig.json. Problem solved by doing in cypress/.eslintrc.js file:

I think the problem is that you are trying to use the deprecated babel-eslint parser, last updated a year ago, which looks like it doesn't support ES6 modules. Updating to the latest parser seems to work, at least for simple linting.

So, do this:

• In package.json, update the line "babel-eslint": "^10.0.2", to "@babel/eslint-parser": "^7.5.4",. This works with the code above but it may be better to use the latest version, which at the time of writing is 7.16.3.
• Run npm i from a terminal/command prompt in the folder
• In .eslintrc, update the parser line "parser": "babel-eslint", to "parser": "@babel/eslint-parser",
• In .eslintrc, add "requireConfigFile": false, to the parserOptions section (underneath "ecmaVersion": 8,) (I needed this or babel was looking for config files I don't have)
• Run the command to lint a file

Then, for me with just your two configuration files, the error goes away and I get appropriate linting errors.

For my version of this error, the issue seemed to be that I was importing a file with an alias in webpack from within the same directory.

To give an example, I had this directory setup:

This works, but since setZoom and setCenter aren't used, it feels like an anti-pattern:

It looks like you have defined custom paths in your TypeScript config (usually tsconfig.json). The import plugin doesn't know about the correct location of the TypeScript config and hence cannot resolve those paths. What you need to do, is to specify the correct path to your TypeScript config via the project parameter in the resolver options:

Ok, so I don't know if it is the correct answer, but finally changing the settings in Eslint helped me to change the type of function for Components. I added the following rule to my .eslintrc.js file:

I originally came up with something that seemed overcomplicated so I asked Titian Cernicova-Dragomir to look it over. He was able to simplify it (as I suspected). It turns out the key was something I'd done quite late in the process of building my original: Using & {initialState?: undefined} in one of two overload signatures to add in undefined to the possible types that the data member of the returned object could have.

Here's the result, with explanatory comments. There's an assumption in there: That you want the setData function not to accept undefined even when there's no initialState (and so TData has undefined in it). But there are instructions for removing that if you want setData to accept TData (even when it includes undefined).

The rule was renamed to valid-describe-callback in eslint-plugin-jest@25.0.0, which you updated past. You will need to rename any config which references the old rule.

See valid-describe: rename to valid-describe-callback (f3e9e9a) https://github.com/jest-community/eslint-plugin-jest/releases/tag/v25.0.0