Docs are full of TypeScript samples nobody tests. An export gets renamed, a property moves, and the sample silently rots — the next developer who copies it fails in their first five minutes, and nobody upstream ever finds out. Snippetcheck type-checks the TypeScript samples in your docs against the npm package you actually published, and reports the ones that no longer compile. Ran it against the AI SDK docs this morning: 18 broken samples, checked 276 of 4,552 extracted samples against ai@7.0.84, skipped 363 (220 do not import ai, 115 before/old examples, 24 historical/migration content, 3 JS/JSX, 1 unparseable). The skipped count is the argument, not a footnote — a checker that flags migration guides and placeholder code is worse than no checker at all. The one worth pointing at directly: eight of the docs pages show import { experimental_generateImage as generateImage } from "ai". TypeScript's own suggestion for the missing export is Experimental_GeneratedImage — a type, not a function. The docs' own prose says the real replacement is generateImage. A tool that trusted the compiler's "did you mean" here would send you to import a type where a function belongs. Honest limit, up front: TypeScript and JavaScript only, nine diagnostic codes, and reports right now are run by hand. If you want yours checked: reply with a docs URL and an npm package name and I'll run it. David

snippetcheck

Find the code samples in your docs that no longer compile

Find the code samples in your docs that no longer compile