TS2724: Module has no exported member named. Did you mean...?

The same failure as TS2305 — the named export doesn't exist — except TypeScript found another real export of the module whose name is close enough to suggest.

Why this happens in documentation specifically

This is the highest-value example on this whole site, so it gets stated plainly rather than summarized: a real, currently-published AI SDK docs page imports `experimental_generateImage`, which no longer exists. TypeScript's suggestion is `Experimental_GeneratedImage` — a real export of the `ai` package. It is also a type, not a function, and following it would produce a second, more confusing error. The package's own documentation prose, elsewhere on the same site, says the actual replacement is `generateImage` — confirmed by testing both names directly: `generateImage` compiles clean, `experimental_generateImage` does not.

TypeScript picked `Experimental_GeneratedImage` because it's textually closer to the broken name than `generateImage` is — string-similarity has no concept of "function vs. type," only edit distance. A reader who trusted the suggestion here would import a type where a function belongs.

A real example

import type { LanguageModelV1Middleware } from "ai";

How to fix it

Treat "Did you mean" as a lead, not an answer — check whether the suggested export is even the same *kind* of thing (function, type, class) as what you're replacing, then check the package's own docs or changelog for the real migration path.

This is exactly why snippetcheck's own report never writes "did you mean" — it renders this field as "TypeScript suggests: X," specifically to avoid implying the tool itself is vouching for it.

Related codes

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