TypeScript TS2769: No overload matches this call

What causes this error

TS2769 fires when a function has multiple overload signatures and the arguments you pass don't match any of them. TypeScript tries each overload in declaration order and collects the failure reasons. When none succeed, it reports TS2769 with the failure details for each overload. This commonly occurs with DOM APIs (addEventListener, createElement), React APIs (useState, useRef), and library functions with complex overloads.

How to fix it

1. 01

   step 1

   Read all overload failure messages

   TS2769 includes a sub-error for each overload that failed. Each sub-error explains why that specific overload didn't match. Find the overload you intended to use and read its specific failure reason — that's the argument you need to fix.

   No overload matches this call.
     Overload 1 of 2, '(event: "click", handler: (e: MouseEvent) => void): void',
       gave the following error:
         Argument of type '"hover"' is not assignable to parameter of type '"click"'.
     Overload 2 of 2, '(event: "keydown", handler: (e: KeyboardEvent) => void): void',
       gave the following error:
         Argument of type '"hover"' is not assignable to parameter of type '"keydown"'.

   Copy
2. 02

   step 2

   Fix the argument type that fails across all overloads

   Often one argument is wrong for all overloads. Fix that argument and the error resolves. Common cases: passing a string literal that doesn't match any accepted union member, or passing an object with wrong property types.

   // addEventListener has overloads for specific event names
   const el = document.getElementById('btn')!
   
   // TS2769: 'clck' doesn't match any overload
   el.addEventListener('clck', (e) => {})  // typo
   
   // Fix: correct event name
   el.addEventListener('click', (e) => {})  // OK

   Copy
3. 03

   step 3

   Check argument count and order

   Different overloads may expect different numbers of arguments. If you're passing too many or too few, no overload will match. Check the function's type signature to see what each overload expects.

   // useState has two overloads:
   // useState<T>(initialState: T): [T, Dispatch<SetStateAction<T>>]
   // useState<T>(): [T | undefined, Dispatch<SetStateAction<T | undefined>>]
   
   // TS2769 when argument type is ambiguous
   const [val, setVal] = useState(null)  // null matches no specific overload cleanly
   
   // Fix: provide the type parameter
   const [val, setVal] = useState<string | null>(null)  // OK

   Copy
4. 04

   step 4

   Handle React component prop mismatches

   In React with TypeScript, JSX elements are type-checked against component prop types. Passing props that don't match any overload of createElement (which JSX compiles to) triggers TS2769. The fix is to correct the props.

   interface ButtonProps {
     variant: 'primary' | 'secondary'
     onClick: () => void
   }
   
   function Button({ variant, onClick }: ButtonProps) {
     return <button className={variant} onClick={onClick}>Click</button>
   }
   
   // TS2769: 'tertiary' not assignable to 'primary' | 'secondary'
   <Button variant="tertiary" onClick={() => {}} />
   
   // Fix: use a valid variant
   <Button variant="primary" onClick={() => {}} />

   Copy
5. 05

   step 5

   Narrow types before calling overloaded functions

   When passing a union type to an overloaded function, TypeScript may not be able to match any single overload. Narrow the union first so TypeScript can pick the right overload.

   // Overloaded function
   function format(value: string): string
   function format(value: number): string
   function format(value: string | number): string {
     return String(value)
   }
   
   const input: string | number = getValue()
   
   // TS2769: union doesn't match either overload
   format(input)  // Error
   
   // Fix: narrow first
   if (typeof input === 'string') {
     format(input)  // matches overload 1
   } else {
     format(input)  // matches overload 2
   }

   Copy

How to verify the fix

• Run tsc --noEmit and confirm TS2769 no longer appears
• Hover over the function call in VS Code to verify the correct overload is selected
• Check that the fix doesn't introduce a different type error downstream