TS2614: Module has no exported member. Did you mean to use a default import?
Module '"<package>"' has no exported member '<name>'. Did you mean to use 'import <name> from "<package>"' instead?You imported a named binding that doesn't exist — same underlying fact as TS2305 — but the module also has a default export, so TypeScript adds a specific suggestion: maybe you meant the default import, under this same local name.
Why this happens in documentation specifically
This fires specifically for packages that export both a default and named bindings — common for SDK client classes, like `export { OpenAI as default } from "./client.js"` alongside the named `OpenAI` export. A docs sample importing the wrong form of a genuinely real export lands here instead of at plain TS2305.
The suggestion clause always echoes back the exact same name you already tried, just in default-import syntax — never a different symbol. That makes it structurally different from TS2724's suggestion, which names an actually different export.
A real example
import { totallyFakeExport } from "zod";How to fix it
Check which form — default or named — the package's current documentation actually shows for this import. Both may be valid; the docs sample may simply have picked the wrong one for the version it was written against.
Related codes
snippetcheck finds diagnostics like this one across a whole documentation site, not just a single sample — see how it works.