Build Components

HomeGet started

Take a part

There is nothing to install from here. Every one of the 137 parts is a file you copy into your project, and after that it is yours — including the bits you disagree with.

Two ways in

1. Copy the files

Open a part, set it up, and copy what the Code tab shows. For React that is one file. For the plain output it is an HTML fragment, a stylesheet and — only when the part needs one — a script. The code you copy is the code the tests ran against.

2. Install it by URL

Every part is also a shadcn registry item, so the CLI can fetch it. Your options travel in the query string, which means the command you copy sets the part up exactly as you left it.

npx shadcn@latest add https://build-components.devstash.me/r/date-picker.json

That is the plain default. The editor gives you the same command with your own options on the end — and the registry applies them to the file before it hands it over, so nothing has to be edited afterwards.

Or by name, and from your AI assistant

Add the namespace to your components.json once, and install any part by its name. The shadcn MCP server reads the same index, so an assistant can find and add parts too.

"registries": { "@build-components": "https://build-components.devstash.me/r/{name}.json" }
npx shadcn@latest add @build-components/date-picker

By name, a part comes with its defaults. Assistants that read llms.txt also get every option of every part, so they can write the address with your options in it.

What your project needs

For the React output: React 19 and Tailwind CSS v4
The files use v4-only syntax — bg-(--dp-accent) rather than bg-[var(--dp-accent)] — and one or two use React 19's own stylesheet hoisting. On Tailwind v3 the classes will not compile.
For the plain output: nothing at all
An HTML fragment, a stylesheet and sometimes a script. No build step, no framework, no package. Each stylesheet sets its own box-sizing and line-height, so it does not need a reset to look right.
No runtime dependency, either way
Nothing here imports a component library. That is the point: there is no version of this to upgrade, and no maintainer to wait for.

Making it yours

Every part draws its colours from custom properties set on its own root, prefixed per part — --dp- for the date picker, --cmd- for the command menu. Change them in one place and nothing else has to be touched.

  • Theme is an option on every part: light, dark, or follow the device. “Follow the device” is the only one that reacts to the operating system, so a page that is deliberately light stays light.
  • An accent colour is corrected before it is used as text, so a colour that would fail WCAG never gets printed. Watch that happen.
  • Money and dates are formatted by hand rather than by locale, because Intl gives the server and the browser different strings and breaks hydration. If you need real localisation, that is the line to replace.

What you may do with it

Every part and template you take from here is under the MIT licence: use it, change it and ship it in anything, free or paid, with no need to ask. The one condition is to keep the copyright and licence notice with the code; the first line of each file points to this page.

It comes as is, with no warranty: it is tested in every output, but you ship it, so test it in your product too. The website, the editor and the page builder themselves are not part of the licence.

The MIT licence
MIT License

Copyright (c) 2026 Adesh Shukla

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.