* fix(react): hide MessageScroller until the opening position applies
A server-rendered transcript paints at scrollTop 0, then jumps after
hydration. Emit data-pending-scroll on first paint and hide the styled
viewport until defaultScrollPosition runs.
* style: format MessageScroller docs tables and class order
* feat(shadcn): add migrate base-color
Add a `base-color` migration that switches a project's base color and
rewrites its theme CSS variables, mirroring `migrate icons`. Only tokens
that still hold the source base color's value are replaced; customized
tokens are left untouched and reported. `--from` defaults to the current
`baseColor`.
* chore: add changeset
* chore: changeset
---------
Co-authored-by: shadcn <m@shadcn.com>
ensureRegistriesInConfig now checks package.json registries before
falling back to the registries index. Registries declared in
package.json are merged into the config in memory and never persisted
to components.json: the components.json write is built from the file
on disk, and init only persists registries discovered from the index.
- getRegistriesConfig now merges registries from both package.json and
components.json, with components.json taking precedence per key.
- registry add now writes to package.json when components.json is not
present, mirroring how registries are resolved.
* fix(shadcn): replace node-fetch with undici
Removes the transitive node-domexception deprecation warning triggered
on install by node-fetch -> fetch-blob. Uses Node's global fetch with
undici.ProxyAgent as the dispatcher when https_proxy is set, preserving
existing proxy support.
Also declares the implicit Node version requirement (>=20.18.1, matching
undici@7's engines field) now that Node 20 is entering maintenance EOL.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* chore: changeset
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(shadcn): expand proxy env-var support via EnvHttpProxyAgent
Switch the registry fetcher from undici.ProxyAgent (single-URI) to
undici.EnvHttpProxyAgent, which honors HTTPS_PROXY, HTTP_PROXY,
NO_PROXY (and lowercase variants). Previously only https_proxy
lowercase was respected.
Extracts the dispatcher selection into createProxyDispatcher in
packages/shadcn/src/registry/proxy.ts, with unit tests covering
all env-var permutations and an integration test that spins up a
local CONNECT-tunneling proxy to verify end-to-end routing and
NO_PROXY bypass.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* chore: update changeset
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(shadcn): add SOCKS and PAC proxy support
Extends the registry's proxy capabilities beyond HTTP/HTTPS to cover
the standard proxy mechanisms users encounter:
- SOCKS4/SOCKS5 via ALL_PROXY=socks5://... (curl convention).
Implementation uses the `socks` package wired into a custom undici
Agent's `connect` factory, so SOCKS routing flows through the same
fetch dispatcher pipeline as HTTP/HTTPS.
- PAC files via PAC_URL, with full PROXY/SOCKS/DIRECT directive
support. PacDispatcher lazily fetches and compiles the PAC script
using `pac-resolver` (running PAC JavaScript in a QuickJS WASM
sandbox via `quickjs-wasi`), then resolves and routes per request.
Detection and routing priority is PAC > SOCKS > HTTP, matching the
specificity of each mechanism (PAC can return mixed directives
per request; SOCKS and HTTP are per-process configurations).
Coverage:
- 14 new unit tests (env-var detection, priority, edge cases)
- 7 new integration tests using a hand-rolled SOCKS5 server, a
CONNECT-tunneling HTTP proxy, and a PAC file server — verifying
end-to-end routing for each mechanism plus per-host PAC directives.
A local pac-resolver.d.ts stub mirrors the v9 surface we use,
because pac-resolver@9 ships its types only via the `exports` map
which the repo's classic `moduleResolution: node` doesn't read.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* chore: update changeset for SOCKS and PAC support
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test(shadcn): tighten proxy integration tests per review
- Replace the dead "proxy-direct" response body in the test proxy's
request handler with a 502 reply. The request callback path was
never exercised (undici only sends CONNECT to the proxy), so the
unreachable JSON body was confusing dead code. Lock the new
CONNECT-only contract in with an explicit test.
- Tighten the NO_PROXY-non-match assertion from `.toHaveLength(1)` +
`.toBe("CONNECT")` to `.toEqual([{ url: originHost, method: "CONNECT" }])`,
matching the parallel HTTP_PROXY test. The looser version would
miss bugs where the dispatcher CONNECTed to the wrong host (e.g.,
the proxy's own address instead of the origin's) — the strict
version catches that bug class.
Both changes per @pomeh's review feedback.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* refactor(shadcn): rescope proxy support to SOCKS only
Per review feedback, split the proxy work: this branch now lands SOCKS
support alone and PAC moves to a follow-up PR.
Removes the PacDispatcher, the PAC directive parser, the PAC_URL env
handling and the pac-resolver type stub, along with the pac-resolver and
quickjs-wasi dependencies (the latter being ~3 MB of WASM). The socks
dependency and the entire SOCKS code path are unchanged, as is
fetchWithProxy's cross-origin redirect hardening.
ALL_PROXY remains SOCKS-only: a non-socks scheme falls through to the
explicit HTTP_PROXY / HTTPS_PROXY variables rather than being absorbed.
Changeset bumped from patch to minor.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011YT4UiAoMUVeF9xaVm9ufi
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: shadcn <m@shadcn.com>
* fix(shadcn): create nested output directories in build
Registry item names can contain path segments (e.g. "extension/foo").
Both build commands wrote <outputDir>/<name>.json without creating the
implied nested directories, so builds failed with ENOENT on clean
checkouts where the output directory does not already exist. Create the
parent directory before writing each item.
Fixes#11321
* chore: format
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Xq2q7jaDcyxyA6YjutStLn
---------
Co-authored-by: shadcn <m@shadcn.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
* feat(shadcn): scope component availability by base
* feat(base-toast): add Base UI toast component
* docs(base-toast): document toast and retire base sonner
* feat(v4): generate cross-library icon mapping from registry placeholders
* feat(shadcn): migrate icons between any icon libraries
* fix(shadcn): harden icon template regexes flagged by CodeQL
* fix(shadcn): replace usage-template regexes with a linear scanner
The tail spacer makes a freshly anchored turn read as "at the end", so
reconcileFollowMode re-armed following-bottom one frame after the anchor
placement and the first streamed chunk yanked the reader off the anchor.
Exclude the anchored-to-message hold from arming, matching the existing
settling-jump exclusion.
Claude-Session: https://claude.ai/code/session_0186fcQpHo1aLQC4wRpwKFFu
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
* feat(create): default design system config to base ui
* feat(www): default docs and init to base ui
* feat(www): default preview styles to base-nova
* feat(shadcn): default init and prompts to base ui
* docs: default to base ui in guides and examples
* docs: add changelog
* chore: changeset
* fix: address base ui default review findings
* fix: init handling
* feat: add migrate-radix-to-base skills
* fix: typo
* feat(@shadcn/react): add message-scroller package
Add the @shadcn/react headless primitives package with MessageScroller
scroll anchoring, streaming follow, history prepend, and jump-to-message
behavior. Includes geometry helpers, use-render utility, and unit,
browser, and perf tests.
* feat(registry): add chat components
Add MessageScroller, Message, Bubble, Attachment, and Marker registry
sources for base and radix, style variants, preview-03 chat blocks,
and registry index wiring.
* feat(v4): integrate chat components into docs site
Wire chat components into the v4 app with docs routes, example preview
pages, message part renderers, markdown support, registry build updates,
and supporting lib utilities.
* feat(examples): add chat component demos
Add base and radix example demos for MessageScroller, Message, Bubble,
Attachment, Marker, scroll-fade, and shimmer.
* docs: add chat component documentation
Add component and utility docs for the chat component set, update docs
navigation, and add the June 2026 chat components changelog entry.
* chore: regenerate registry JSON output
Rebuild public registry artifacts for all style variants with the new
chat components.
* chore(release): add @shadcn/react publish and CI pipeline
Add Changesets prerelease workflow, browser test job, RELEASING docs,
and monorepo wiring for publishing @shadcn/react independently from
the shadcn CLI.
* docs: fix display of component preview on mobile
* fix
* fix
* docs: add message scroller docs
* style: format
* fix
- Search across multiple registries and make the registry argument
optional: omit it to search every registry configured in components.json
(builtins like @shadcn excluded). Without a components.json or configured
registries, a clear usage error is printed.
- Add a --type filter (accepts "ui" or "registry:ui", comma-separated)
with validation against the known item types.
- Fetch registries concurrently with a capped worker pool, preserving
result order.
- Tolerate per-registry failures when searching all configured registries
(reported in a structured `errors` field); exit non-zero when every
registry fails. Usage errors print directly instead of routing through
handleError.
- MCP parity: optional registries (search-all), a `types` filter, and type
validation across the search/list/examples tools.
- Keep the public registry surface to `searchRegistries` and make it
self-contained (clears its own context, useCache defaults to false).
- Consolidate search formatting into registry/search, add the `errors`
field to searchResultsSchema, and update the skill docs.
github-actions[bot]