Updated react-scripts from 3 to 4.0.1 with all underlying packages (react@17, typescript@4.1 and eslint@7.14), now it shows Failed to compile. in the console with tons of prettier problems like they are errors. Used to run fine before, showing only Eslint warnings. Also if I hit save on any clean file under watch it recompiles fine (but again, used to show Eslint warning, which I would like to see there). Went through their docs and didn't find a way to configure this behavior, can it be?
top of page
bottom of page
It's possible that the update to react-scripts 4.0.1 introduced changes to the default configuration for eslint and Prettier. The error messages you're seeing could be related to changes in the way that eslint and Prettier are interacting with each other.
To troubleshoot this issue, you may want to try the following steps:
Check the console output for specific error messages that could help identify the root cause of the issue.
Review the updated documentation for eslint and Prettier to see if any changes were made to their default configurations that could be impacting your codebase.
Check your project's configuration files (such as .eslintrc, .prettierrc, and tsconfig.json) to ensure that they are properly configured for the updated versions of eslint and Prettier.
Consider using a tool like eslint-config-prettier to disable any eslint rules that conflict with Prettier's formatting rules.
Verify that all of your project's dependencies are up-to-date and compatible with the updated versions of react-scripts.
If you're still having issues, you may want to consider reaching out to the community forums or support channels for react-scripts or eslint/Prettier to see if anyone else has experienced similar issues and has any suggestions for troubleshooting or configuration changes.
In summary, the update to react-scripts 4.0.1 may have introduced changes that are impacting the way eslint and Prettier interact with each other. By reviewing documentation, checking configuration files, and troubleshooting the specific error messages you're seeing, you may be able to identify and resolve the issue.