TS1192: Module has no default export

You wrote a default import — `import x from "pkg"` — against a module that only has named exports, no default. The mirror image of TS2614: there, a named import against a default-exporting module; here, a default import against a module with none.

Why this happens in documentation specifically

A common source in real documentation: a sample written for one bundler configuration (where `esModuleInterop`-style default-import syntax against a CJS-shaped module is tolerated) shown to a reader using a stricter one, or a package that dropped its default export in a later major version without every sample being updated.

A real example

import format from "date-fns";

How to fix it

Switch to whatever named import the package's current declarations actually expose — check its `.d.ts` root export list, since by definition there's no default to fall back to.

Related codes

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