Skip to content

[pull] main from chakra-ui:main - #297

Merged
pull[bot] merged 1 commit into
code:mainfrom
chakra-ui:main
Aug 20, 2026
Merged

[pull] main from chakra-ui:main#297
pull[bot] merged 1 commit into
code:mainfrom
chakra-ui:main

Conversation

@pull

@pull pull Bot commented Aug 20, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

…3983)

* fix(website): render llms routes for one framework instead of four

velite expanded every `<Example />` and `<ComponentTypes />` at build time,
where there is no framework, so it emitted a `#### React` / `#### Vue` /
`#### Svelte` / `#### Solid` block for each. The request-time code that does
this per framework then found no tags left to expand, so llms-react.txt
shipped 505 Vue, 562 Solid and 494 Svelte markers, and llms-full.txt grew to
20,037,108 bytes and failed the Vercel 20MB prerender cap by 37KB.

velite now leaves those tags in place and the request-time path resolves
them, so each file carries only its own framework: 4.78MB down to 1.4MB.
llms-full.txt is removed and redirects to llms.txt, matching TanStack, who
serve their index at both URLs for the same reason. The spec never defined
llms-full.txt.

Also expands the tags the routes were dropping on the floor: `<ExampleCode />`
(9 tags, which left Locale and Environment with no code samples at all),
`<ComponentTypes />` carrying a `replace` map (Segment Group had no props
documented), `<ContextType />` for components with no zag machine, and
`<ThemeImage />`.

Pages now resolve per framework, so each bundle carries its own changelog
rather than @ark-ui/mcp's 829 bytes, and the changelog glob no longer treats
mcp as a framework. Fixes the format-number page id, which did not match its
sidebar entry and dropped the page from llms.txt and the sitemap.

llms.txt gains the H1, summary and section structure every comparable
project uses, links the four bundles, and prefixes repeated titles with
their framework.

Claude-Session: https://claude.ai/code/session_0133qcH6rpUR3edEeGJSxsF1

* fix(scripts): format the example registry before writing it

The generator wrote output that `prettier --check` rejects, so every website
build left the tree dirty and failing lint. Reverting that churn also
discarded real content: the committed registry was missing six examples,
including signature-pad/controlled, which components/signature-pad.mdx
references and so could not load.

Formats with the repo config resolved from the output path, and regenerates.
Two runs now produce identical bytes.

Claude-Session: https://claude.ai/code/session_0133qcH6rpUR3edEeGJSxsF1

* feat(scripts): check llms response sizes in CI

Vercel rejects a prerendered response over 20MB and `next build` does not
catch it, so llms-full.txt only failed at deploy. Building the site in CI to
measure would cost minutes, so this bounds the responses from their inputs:
a llms-<framework> response is the page corpus with one framework's examples
and prop tables inlined, so corpus + examples + types is an upper bound.

Currently 1.95MB against a 12MB budget.

Claude-Session: https://claude.ai/code/session_0133qcH6rpUR3edEeGJSxsF1

* docs(svelte): add the missing popover factory example

React, Solid and Vue all have this example; Svelte did not, so the
composition guide rendered "Example not found" for Svelte readers on both
the docs page and in llms-svelte.txt.

Uses the snippet form of `asChild` that the sibling as-child example uses,
since the Svelte factory takes `as` and renders a snippet rather than
exposing an `ark.span` proxy.

Claude-Session: https://claude.ai/code/session_0133qcH6rpUR3edEeGJSxsF1
@pull pull Bot locked and limited conversation to collaborators Aug 20, 2026
@pull pull Bot added the ⤵️ pull label Aug 20, 2026
@pull
pull Bot merged commit 329cb11 into code:main Aug 20, 2026
5 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant