// src/main.jsx import app from './App.jsx'; // ❌ Capital 'A' in the file, lowercase 'a' here Use code with caution. Copied to clipboard
This error means your bundler found the file you asked for, but it couldn't find a variable or component named "App" inside that file. This usually boils down to the difference between and Named exports. 1. Check Default vs. Named Exports
import App from './App'; import App from './App.jsx'; import App from './components/App'; no matching export in fs src app.jsx for import app
By systematically searching for bad imports, inspecting your bundler configuration, and clearing caches, you can resolve this error in minutes. More importantly, adopting strict linting rules and avoiding core module aliases will prevent it from ever happening again.
import App from './App.jsx'; // ✅ Correct for default exports Use code with caution. Copied to clipboard // src/main
Sometimes this error triggers if App.jsx imports something from main.jsx , while main.jsx is also importing App.jsx . This creates a "loop."
If using import App , does App.jsx have export function App ? Are there any typos in the word "export" or "default"? Is the file path in the import statement 100% correct? To help you get this running, could you tell me: Are you using ? More importantly, adopting strict linting rules and avoiding
If you are exporting the component without the default keyword, you must use curly braces in your import. In App.jsx: export function App() ... In main.jsx: import App from './App' (Note the ) 2. Case Sensitivity Issues
The error is a classic case of module resolution gone wrong. While the message seems to blame the fs module, the real issue is almost always in your import statements, bundler aliases, or IDE auto-imports.
Any import of fs will resolve to your mock file. If that mock file doesn’t export App , the error appears.