Why are you using your own eslint related files instead of the eslintConfig that is already present in package.json? Did you remove the config from package.json or do you keep it there, having two eslint configurations? Is your solution still using CRA's internal mechanisms or is it something completely custom?
I'm a full stack web engineer with a strong front-end focus. I'm passionate about making the user's experience on the web more accessible, faster, and easier to use.
I'm not using an eslintConfig in my package.json. Using the .eslintrc.json is the only place I have added any configurations. This is just my preference, eslintConfig in package.json is also a valid approach. It just depends on how you like to structure your project
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Why are you using your own eslint related files instead of the
eslintConfigthat is already present inpackage.json? Did you remove the config frompackage.jsonor do you keep it there, having two eslint configurations? Is your solution still using CRA's internal mechanisms or is it something completely custom?I'm not using an
eslintConfigin my package.json. Using the.eslintrc.jsonis the only place I have added any configurations. This is just my preference,eslintConfiginpackage.jsonis also a valid approach. It just depends on how you like to structure your project