TypeScript incorrectly says return is not assignable to an intersection containing all the required props

Bug Report

🔎 Search Terms

& generic intersection omit spread

🕗 Version & Regression Information

• This is the behavior in every version I tried, and I reviewed the FAQ for entries about generics

⏯ Playground Link

Playground link with relevant code

💻 Code

export interface BaseProps {
  id?: string;
  name: string;
}

export type PropsWithId<P extends BaseProps> = Omit<
  P,
  'id'
> & { id: string };

export default function usePropsWithId<P extends BaseProps>(
  props: P
): PropsWithId<P> {
  const { id: idProp, name, ...other } = props;
  const id = idProp ?? `${name}-id`;

  return { id, name, ...other };
}

🙁 Actual behavior

The return line gets this TypeScript error:

Type '{ id: string; name: string; } & Omit<P, "id" | "name">' is not assignable to type 'PropsWithId<P>'.
  Type '{ id: string; name: string; } & Omit<P, "id" | "name">' is not assignable to type 'Omit<P, "id">'.

This doesn't make sense since PropsWithId<P> is Omit<P, 'id'> & { id: string };

🙂 Expected behavior

This should work without a TypeScript error.

Start with the linked TypeScript Playground and the generic intersection example in the issue, then trace how the checker evaluates the returned object against PropsWithId

. The issue names no repository files or tests; done means the sample compiles without the reported assignability error while preserving the expected PropsWithId

type.