TypeScript cannot name the type of an exported MUI styled component
The inferred type of 'X' cannot be named without a reference to '...'. This is likely not portable. A type annotation is necessary.Short answer
TypeScript must write the component's type into a .d.ts file, but that type lives in a package you did not import directly. The fix is to annotate the exported value with an explicit type, or to list the package that owns the type as a direct dependency in package.json.
Fix it fast
1Find out which cause you have
Confirm that declaration output is what triggers the error, and read which package the message names.
npx tsc --declaration --emitDeclarationOnly --outDir dts-check2Match what you see, then jump to its fix
What does the error look like?
The inferred type of 'X' cannot be named without a reference to '...'. This is likely not portable. A type annotation is necessary.error TS2742
Cause 1 of 2
The exported value has no type annotation
1Check
The TypeScript team says an explicit type annotation on the flagged node is the main answer, and the error message itself recommends it.
grep -rn "export const .* = styled(" src/2Fix
Give the export a type. A simple route is to type it as the component you wrapped.
import { styled } from '@mui/material/styles';
import Button from '@mui/material/Button';
export const CustomButton: typeof Button = styled(Button)({
// styles
});3Verify
Run the declaration check again. TS2742 is gone.
npx tsc --declaration --emitDeclarationOnly --outDir dts-checkConfirmed by github.com
Cause 2 of 2
The package that owns the type is only an indirect dependency
1Check
A declaration file needs a type from an indirect dependency, and TypeScript cannot always find a path to it. Look at which package the message names and whether it is in your package.json.
npm ls @mui/types @emotion/styled2Fix
Declare that package as a direct dependency. The TypeScript team notes that from 5.5, the names can be generated when the dependencies are direct.
npm install @emotion/styled @emotion/react3Verify
Run the declaration check again.
npx tsc --declaration --emitDeclarationOnly --outDir dts-checkConfirmed by github.com
How do I stop it coming back?
- Annotate the exported values of any library or shared package that emits .d.ts files.
- List every package whose types leak into your public API as a direct dependency.
- Keep one copy of each types package; check with npm ls after upgrades.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
TypeScript refuses JSX because the jsx option is not set
TS17004: Cannot use JSX unless the '--jsx' flag is provided.
TypeScript compiles JSX only when you name the file with a .tsx extension and enable the jsx compiler option.
2 causes, each with a fixWeb apps
TypeScript rejects a component that returns an array or other non-Element
Its return type 'Element[]' is not a valid JSX element.
TypeScript before 5.1 required every component to return JSX.Element or null, so arrays, strings and Promises were rejected even though React renders them.
2 causes, each with a fixWeb apps
ESLint says it cannot resolve a path to a module that does exist
Unable to resolve path to module 'react'. import/no-unresolved
import/no-unresolved fails when eslint-plugin-import cannot find the file or package on disk with its resolver.
4 causes, each with a fixWeb apps
ESLint reports no-unused-vars for React components and imports that are used
no-unused-vars reported for a component that is rendered as a JSX tag
ESLint's core no-unused-vars does not see variables used only as JSX tags, so a component imported and rendered as <Hello /> looks unused.
3 causes, each with a fixWeb apps
TypeScript rejects MUI Data Grid columns that set a type
A TypeScript error inside a column's renderCell callback
A columns array declared without a type is inferred with type as a plain string, which the Data Grid's column type union does not accept.
2 causes, each with a fixWeb apps
The renderInput prop stopped working on the MUI X DatePicker
The custom TextField (variant, size, helperText) is ignored
renderInput was removed from the MUI X date pickers in version 6.
3 causes, each with a fix