Files
upstream-shadcn-ui/apps/v4/content/docs/changelog/2026-07-dynamic-search.mdx
upstream-mirror 1416db152c
All checks were successful
Release / Create Version PR or Publish Stable Release (push) Has been skipped
Release / Publish Prerelease to NPM (push) Has been skipped
Monitor Registries / Monitor registry health (push) Has been skipped
snapshot of https://github.com/shadcn-ui/ui.git (main, 2026-09-15; blobs > 131072B omitted)
2026-09-15 22:44:43 +05:00

45 lines
1.0 KiB
Plaintext

---
title: July 2026 - Dynamic Search
description: Registries can now handle search server-side.
date: 2026-07-31
---
**Registries can now handle search server-side.**
When you run `shadcn search`, the CLI forwards the search parameters to your
registry as query params:
```txt
GET /r/registry.json?q=button&limit=50&offset=0
```
Return the matching items with a `pagination` object and the CLI uses your
results as-is. This makes search fast for large registries: no more downloading
the full catalog to search it.
```json title="registry.json?q=button&limit=1"
{
"name": "acme",
"homepage": "https://acme.com",
"items": [
{
"name": "button",
"type": "registry:ui",
"description": "A button component."
}
],
"pagination": {
"total": 12,
"offset": 0,
"limit": 1,
"hasMore": true
}
}
```
Dynamic search is opt-in. Static registries ignore the query params and keep
working without any changes.
See the [Dynamic Search](/docs/registry/dynamic-search) docs for the full
guide.