prop-types | Runtime type checking for React props and similar objects | Frontend Framework library

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.

It appears you are using react-router-dom@6 so there are no longer any route props. In other words, props.match is undefined. Reading into props.match.params then throws the error.

Use the useParams hook to access the date route param.

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:

You cant retrieve the information you are looking for by reading the propType properties. Each item in the propTypes is actually a validation wrapper function that obscures the actual type validation.

There is a way to achieve what you are looking for, but it isn't particularly pretty. See this answer.

Another option for your scenario is to create and export another static property with your component that includes the information you need. Then create a utility method to map your property data into PropTypes

For example:

React-router-dom is hook based under the hood, but hooks weren't introduced until React v16.8.4. You are still using React v16.6.3. Update to a newer version of React (react) and ReactDom (react-dom).

ESLint 8.0.0 comes with a breaking change for rules that provide suggestions. There is nothing you can put into your .eslintrc.js to make it work if you use rules that haven't been updated to work after this change.

What you can do:

• Use ESLint 7 until the plugin is updated to work with ESLint 8.
• In case of eslint-plugin-react-hooks, the offending rule has already been updated (check this line on GitHub), it's just that there hasn't been a stable release of the package since. However there have been daily alpha releases, at the time of writing the latest version is 4.2.1-alpha-c3a19e5af-20211014. If you really need both ESLint 8 and this plugin, you can use an alpha version until the next stable version comes out.

Asked the NAtive Base creators about it: https://github.com/GeekyAnts/NativeBase/issues/4011

Basically they say that it's a problem only hen using npm and not yarn, so they ask that we use yarn for now.

but i dont know what is the node version on github actions i can not reproduce the error in my local, because of the version are not the same

You could use setup-node action to make the version exactly same with your local:

You need to provide the full value object for the defaultValue to work. This should work: