Keywords: React | ESLint | Windows | Deployment
Abstract: This article addresses the common error 'Plugin react was conflicted' during React app deployment, caused by path casing inconsistencies on Windows. It explains the cause, provides a permanent solution by ensuring correct folder casing, and offers temporary workarounds to help developers avoid deployment failures.
Problem Description
When deploying a React application with Create React App, developers often face a compilation error with the message: Plugin "react" was conflicted between "package.json » eslint-config-react-app ». This error prevents the app from starting and displays a blank page or error on localhost.
Root Cause Analysis
The primary cause of this issue is a path casing conflict specific to Windows. For example, the project path might be C:\Users\Ruben\desktop\reactapp\test (with lowercase "desktop"), while the node_modules directory or ESLint configuration expects C:\Users\Ruben\Desktop\Reactapp\test (with uppercase "Desktop" and "Reactapp"). Windows file systems are case-insensitive, but Node.js and ESLint can be case-sensitive in certain contexts, leading to this conflict.
Permanent Solution
Based on the accepted answer, the solution is to ensure that the folder path matches exactly what is stored in node_modules. One effective method is to open the project folder directly through an IDE like Visual Studio Code. For instance, navigate to the folder and use "Open with Code" to set the correct casing.
Temporary Workaround
As a supplementary reference, some users have found that simply saving the package.json file in VS Code (by pressing Ctrl+S) can temporarily resolve the issue. However, this may need to be repeated each time the problem occurs, making it less ideal for long-term use.
Conclusion and Recommendations
To avoid such deployment errors, it is recommended to maintain consistent path casing in Windows environments. Using tools that handle path casing correctly, such as modern IDEs, can prevent this conflict. Developers should be aware of Windows-specific quirks in cross-platform projects.