Open Brianzchen opened 2 years ago
I'm having this problem too: https://stackoverflow.com/q/70397587/470749
+1
same here, please resolve asap
@iansu who would be the best person to look into this?
I'm having same issue in CRA 5.0.0 and eslint 8.6.0
fwiw, I had this same issue and upgrading my node from v12 to v17 (latest) fixed it
One thing you can do as a quick fix is use a different eslint config, you can find a property in package.json that should look something like this
"eslintConfig": {
"extends": [
"react-app",
"react-app/jest"
]
},
You can then remove the extends values and replace it with whatever your preference is like airbnb which is a popular one
Had the same issue with node12. Switching to a more recent version of nodejs solves the issue. create-react-app has officially dropped support for node12 since v5. See https://github.com/facebook/create-react-app/blob/main/CHANGELOG.md#breaking-changes
@iansu it looks like you're a maintainer. Can we please get at least from response here? This also blocks people from using flow enums
Had the same issue with node12. Switching to a more recent version of nodejs solves the issue. create-react-app has officially dropped support for node12 since v5. See https://github.com/facebook/create-react-app/blob/main/CHANGELOG.md#breaking-changes
DISABLE_ESLINT_PLUGIN=true react-app-rewired start
can avoid this error, and even node10 can work, for only eslint@8
is using Module.createRequire
, ref to doc Upgrade to react-scripts@5 and Add Web Workers support and APP PixelShapeRN commit Add Web Workers support for CRA v5 (and Webpack 5)
Describe the bug
Hi 👋 , I'm a maintainer on flow-typed and a new flowtype eslint library
eslint-plugin-ft-flow
A user on stack overflow reported an issue with
eslint-plugin-flowtype
ineslint-config-react-app
when usingcreate-react-app
. Full information can be read hereI've already fixed the issue in eslint-plugin-ft-flow and provide the library active maintenance compared to the original. Would the team at create-react-app be interested in swapping over to the new library to solve this and future issues.