Minified React error #130
Element type is invalid (Production Minified variant #130).
Usually happens because:
- ☑ Default vs Named export mismatch in prod
- ☑ Path case-sensitivity issues on server filesystems
- ☑ Circular module references
🔍 Quick Checklist:
📊 Where this usually happens (estimated occurrence)
What is Minified React error #130?
Minified React error #130 is the production equivalent of 'Element type is invalid'. It means React expected a component type but received undefined or an object during production mounting.
Common Causes
- Mismatched exports or import typings in production code.
Common Mistakes
- Importing components with naming capitalization mismatches.
How to Fix
Framework-Specific Examples
No framework examples required for this informational status.
Production Mismatch
// Mismatched default/named import in production bundle
import { MyBtn } from './MyBtn';
return <MyBtn />;Correct: Match exports
import MyBtn from './MyBtn';
return <MyBtn />;Best Practices
- Use auto-imports and lint rules to verify components resolution.
Frequently Asked Questions (FAQ)
Q: What is Minified React error #130?
It is the production version of the 'Element type is invalid' error, thrown when a component resolves to undefined during render.
Q: Why does this happen in production but not in dev?
Usually because of differences in tree-shaking, packaging, or different path case resolutions on production servers.
Q: How do I debug Minified React error #130?
Follow the console URL to see details, then trace import blocks in components that were recently updated or refactored.
Q: Can circular imports trigger this?
Yes. Circular dependencies result in undefined exports, triggering error #130 when mounting.