Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

leadtype@0.2.0

Minor Changes

• e923e9f: Add leadtype/next framework adapter and formalize the core/adapter boundary.

  leadtype/next exposes three server-only helpers for Next.js App Router: createGenerateStaticParams(...), createLoadPageData(...), and createDocsRouteHandler(...). The route handler wraps createAgentMarkdownResponse so a docs app can serve raw markdown, handle Accept: text/markdown negotiation, and detect AI user agents from a one-line route.ts. The companion leadtype/next/client subpath exports a useLeadtypeSearch React hook plus a framework-free createSearchClient factory that lazy-loads search-index.json / search-content.json and runs BM25 per keystroke.

  react is now an optional peer dependency for leadtype/next/client. Server-only consumers never pull in React.

  Documents the core/adapter boundary in a new docs/reference/architecture page: leadtype core has zero framework runtime deps, adapters live at flat leadtype/<framework> subpaths, and no leadtype package — core or adapter — ever ships rendered DOM. State primitives (hooks, composables, stores, handler factories) are allowed; <SearchBox>-style components are not. The docs also name the planned native adapter shapes for Nuxt, SvelteKit, Astro, TanStack Start, Vue search, and Svelte search without exporting those APIs yet. The boundary is now enforced by tests in packages/leadtype/src/internal/package-surface.test.ts that scan import graphs and fail if framework runtimes leak into core or one adapter imports from another.

Patch Changes

• c7fcbf6: Add first-class docs i18n support with locale-aware generation, localized source loading, per-locale search/LLM/readability artifacts, and a new leadtype/i18n helper surface. Locale-scoped search generation now uses URL-path document ids to align generated indexes with the source API.

• 844a94d: Default <ExtractedTypeTable> and <AutoTypeTable> path resolution to the Leadtype source root instead of process.cwd()/docs.

  This fixes generated docs for source roots such as .c15t or .leadtype, where path="./packages/..." should resolve against the configured source root. Source-MDX consumers can now pass typeTableBasePath / typeTableStrict through createDocsSource() or use createMdxSourcePlugins() for bundler-level configuration. Failed type extraction now emits a visible warning by default and can fail generation in strict mode.

  This changes the bare mdxSourcePlugins default for bundler consumers: when Leadtype can see the source MDX file path, it derives the base path from the first docs path segment instead of always using process.cwd()/docs. Projects that intentionally keep referenced TypeScript files under their docs folder should switch to createMdxSourcePlugins({ typeTableBasePath: path.resolve(process.cwd(), "docs") }).