feat: implement TypeGen support

[Copilot]

Adds full Sanity TypeGen support, mirroring the approach from @portabletext/react (PR #309). Purely type-level — zero runtime changes.

Changes

• Generic component interfaces — PortableTextHtmlComponents<B>, PortableTextComponents<B>, and PortableTextOptions<B> now flow B from the value parameter through to component handlers
• Type inference machinery — 3-branch conditional component map types that gracefully degrade: precise literals → narrowed handlers, wide/unknown → loose Record<string, ...>, no custom members → fallback
• New public utility types:
  • InferComponents<T> — forgiving component map inferred from value type (extra handlers allowed)
  • InferStrictComponents<T> — strict mode requiring all custom handlers, rejecting unknown ones
  • InferValue<T> — recursively extracts PT array item types from any TypeGen query result
  • DefaultPortableTextBlockStyle, DefaultPortableTextListItem, DefaultPortableTextMark
• Type-level tests covering inference for custom types, marks, blocks, lists, strict mode, and InferValue

Usage

import {toHTML} from '@portabletext/to-html'
import type {InferComponents} from '@portabletext/to-html'

// Components are now type-aware when value type is known
const components = {
  types: {
    // `value` is narrowed to ImageBlock
    image: ({value}) => `<img src="${value.url}" alt="${value.alt}" />`,
    code: ({value}) => `<pre><code>${value.code}</code></pre>`,
  },
} satisfies InferComponents<typeof data.content>

toHTML(data.content, {components})

Backward compatible — all generics default to any, so existing untyped usage is unchanged.

[changeset-bot]

🦋 Changeset detected

Latest commit: a4e1a37

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@portabletext/to-html	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[stipsan]

@copilot no no, I want you to setup the same exact testing suite https://github.com/portabletext/react-portabletext/tree/d15decca09351dcef693373746d31bacf052d3dd/test/typegen where the only difference is that instead of assertions with react like:
;<PortableText value={bio} components={components} />
you will be doing
toHTML(bio, {components})

Also, the release notes in your changeset/typegen-support.md should be exactly like https://github.com/portabletext/react-portabletext/blob/e59cacb5db777381517a19307512fdb12ce61c9e/.changeset/typegen-component-inference.md

[Copilot]

@copilot no no, I want you to setup the same exact testing suite https://github.com/portabletext/react-portabletext/tree/d15decca09351dcef693373746d31bacf052d3dd/test/typegen where the only difference...

Done in a4e1a37. Set up the same exact test suite from test/typegen/ in react-portabletext, with all supporting files (sanity.cli.ts, sanity.config.ts, sanity.types.ts, schema.json). The typegen.test-d.ts mirrors the React test file but uses toHTML(content ?? [], {components}) instead of <PortableText value={content} components={components} />. The changeset now matches the react-portabletext format. All 73 type tests pass.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​sanity/​client@​7.22.0
	groq@​5.24.0

View full report