TS2561: Object literal may only specify known properties. Did you mean to write...?

Object literal may only specify known properties, but '<name>' does not exist in type '<type>'. Did you mean to write '<suggestion>'?

The same excess-property failure as TS2353, with a spelling suggestion attached — usually because the key you wrote is one character off from a real property on the type.

Why this happens in documentation specifically

The message wording is easy to misparse: it reads "Did you mean to write X?", not "Did you mean X?" — a small but real difference from TS2551's phrasing that this project's own extraction logic got wrong on first attempt and had to fix, because it's genuinely a different string to match, not a formatting variation.

A real example

ai@7.0.66
const result = await embed({ model: "text-embedding-3-small", value: "hi", abortSignall: undefined });
Object literal may only specify known properties, but 'abortSignall' does not exist in type '{ model: EmbeddingModel; value: string; maxRetries?: number; abortSignal?: AbortSignal; headers?: Record<string, string>; providerOptions?: SharedV4ProviderOptions; ... 6 more ...; _internal?: { ...; }; }'. Did you mean to write 'abortSignal'?

How to fix it

Same caveat as TS2551: the suggestion is a spelling-distance guess over the type's real keys, not a confirmed answer. It's most trustworthy for the case it's built for — an actual typo, like the real example below (`abortSignall` → `abortSignal`, one duplicated letter) — and least trustworthy when the real cause is a genuine rename rather than a typo.

Related codes

snippetcheck finds diagnostics like this one across a whole documentation site, not just a single sample — see how it works.