React developers have had shadcn/ui for a while: good-looking components, accessible by default, and code you own. I work in Angular, and I wanted the same thing for Angular. Same classes, same variants, same feel, and current Angular, not something ported from an older version.

I couldn't find a close match, so I built it. It's called Ivorie, it's MIT, and version 1.4 is on npm today.

This post shows what it does with real code you can paste.

Ivorie is an independent project. It's not affiliated with shadcn/ui. It ports shadcn/ui's design (MIT) to Angular, with credit.

What you get

  • 53 components with the shadcn/ui look and behavior. Keyboard and ARIA follow Radix patterns.
  • Angular 22 only. Signal inputs, model(), zoneless, SSR. It also works in NgModule apps.
  • Tailwind CSS 4.
  • Two ways in. Install @inlaylab/ivorie from npm and get updates. Or run the ivorie CLI, which copies the source into your app so you can edit it.
  • 10 styles (shadcn's five plus glass, brutal, aurora, bento and mono), 7 base colors, 26 fonts, 5 radius options.
  • 5 icon libraries: Lucide, Tabler, Phosphor, Hugeicons, Remix.
  • A data table with sort, pagination, filter, selection and column visibility. It runs in the browser or against your API.
  • 19 blocks: login, sign-up, sidebar and dashboard pages, already wired.

Path 1: the npm package

npm i @inlaylab/ivorie @angular/cdk @lucide/angular npm i -D tailwindcss @tailwindcss/postcss tw-animate-css 
/* src/styles.css */ @import "@inlaylab/ivorie/styles/theme.css"; @import "@inlaylab/ivorie/styles/style-nova.css"; 

Add class="style-nova" to <body>. Then import only what you use. Each component has its own entry point, so your bundle carries only those:

import { Component } from '@angular/core'; import { IvButton } from '@inlaylab/ivorie/button'; @Component({ selector: 'app-root', imports: [IvButton], template: `<button ivButton>Save</button>`, }) export class App {} 

The full setup, with the Tailwind config, is on the Installation page.

Path 2: copy the source and own it

This is the shadcn way. The code lands in your repo. Change anything.

npx ivorie init npx ivorie add button dialog 

init sets up the theme, the style and components.json. add copies components to src/app/ui by default (--path changes that). You can even pick your own selector prefix with --prefix.

Both paths come from one source. The CLI copies from the same library code that npm ships, so they don't drift apart.

A sortable table in 30 lines

The data table isn't one big component. It's five small features: ivSort, ivFilter, ivPagination, ivRowSelection and ivColumnVisibility. Rows go in and rows come out, as signals. Use one, or all five. The cells stay in your template.

Here's sorting on its own:

import { ChangeDetectionStrategy, Component, signal } from '@angular/core'; import { IV_DATA_TABLE_IMPORTS, IvColumnDef, ivSort } from '@inlaylab/ivorie/data-table'; interface Release { version: string; name: string; } const RELEASES: Release[] = [ { version: '1.2.0', name: 'Playground' }, { version: '1.10.0', name: 'Later work' }, { version: '1.0.0', name: 'First release' }, ]; const COLUMNS: IvColumnDef<Release>[] = [ { id: 'version', header: 'Version', accessor: (r) => r.version, sortable: true }, { id: 'name', header: 'Name', accessor: (r) => r.name, sortable: true }, ]; @Component({ selector: 'app-releases', imports: [IV_DATA_TABLE_IMPORTS], changeDetection: ChangeDetectionStrategy.OnPush, template: ` <iv-table class="rounded-lg border"> <thead ivTableHeader> <tr ivTableRow> @for (c of columns; track c.id) { <th [ivDataTableSort]="c.id" [sort]="sort">{{ c.header }}</th> } </tr> </thead> <tbody ivTableBody> @for (r of sort.rows(); track r.version) { <tr ivTableRow> <td ivTableCell class="font-mono">{{ r.version }}</td> <td ivTableCell>{{ r.name }}</td> </tr> } </tbody> </iv-table> `, }) export class Releases { protected readonly columns = COLUMNS; protected readonly sort = ivSort(signal(RELEASES), { columns: COLUMNS, initial: { id: 'version', desc: false }, }); } 

The sort header sets aria-sort and works with the keyboard. Versions sort as numbers, so 1.10.0 comes after 1.2.0.

Server mode

When the data lives on your server, switch to mode: 'server'. The table stops sorting and paging in the browser. Instead it gives you one query() signal with the page, sort and filter. Feed that to resource() or httpResource():

protected readonly table: IvDataTable<Order> = ivDataTable<Order>({ mode: 'server', data: computed(() => this.page().rows), rowCount: computed(() => this.page().total), columns: COLUMNS, getRowId: (o) => String(o.id), pageSize: 5, }); protected readonly orders = resource<OrderPage, IvDataTableQuery>({ params: () => this.table.query(), loader: ({ params, abortSignal }) => fetchOrders(params, abortSignal), }); 

It's the same API in both modes. The full example, with the loading and empty rows, is on the data table page.

A login page in one command

Blocks are whole pages. They're wired, not just markup: reactive forms with validation, typed outputs, and pending and error inputs.

npx ivorie add login-01 

This writes the page to src/app/blocks/login-01/. It also adds the components the page needs, fixes the imports, and renames the icons to your icon library. All that's left is your auth call:

@Component({ selector: 'app-login-01', imports: [LoginForm], template: ` <div class="w-full max-w-sm"> <app-login-01-form (submitted)="login($event)" (provider)="loginWith($event)" /> </div> `, }) export class Login01 { protected login(value: LoginValue): void { // Call your auth API here, then navigate. } protected loginWith(provider: 'google' | 'github' | 'apple'): void { // Start your OAuth flow here. } } 

There are 19 blocks: five logins, five sign-ups, eight sidebars and a dashboard. See them live at /blocks.

Make it look like your product

Open the playground. Pick a style, base color, font, heading font, radius and icon library. Real components update as you click. Then copy one command:

# new app npx ivorie init --preset ivp1_… # existing app: change the whole look npx ivorie apply ivp1_… 

The ivp1_… code holds your whole look, so you can share it with your team or paste it in an issue. Flags work too:

npx ivorie init --style glass --base-color zinc --radius large --icon-library tabler 

Changing icon libraries later? npx ivorie migrate icons --from lucide --to tabler renames the icons in your own templates as well.

A note on the new styles: glass uses backdrop-filter. Where that isn't supported, or the user asks for reduced transparency, it turns solid. Every style has a test that checks text contrast (4.5:1 or more) for every base color, in light and dark mode.

How it's built

A few choices you may care about:

  • Signals all the way down. input(), model(), output(), computed(). No @Input() decorators. A lint rule blocks them.
  • No @angular/animations. Motion is CSS through tw-animate-css.
  • SSR is tested on every change. The docs app is server-rendered, and a smoke test loads every page in a real browser.
  • One command for every gate. npm run check runs every build, the unit specs (Vitest, with axe for accessibility), SSR, the package and CLI tests, and the lint rules.
  • The registry uses the shadcn registry JSON format.
  • Releases carry npm provenance and are published from GitHub Actions.

What's next, and how you can help

  • 1.5: AI-ready. An AGENTS.md that ivorie init writes, llms.txt for the docs, and an MCP server so coding agents can browse and add components.
  • 1.6: charts (line, area, bar, pie) that follow the theme and render on the server.

I'd love help with these, and with the smaller issues labeled good first issue. There are new blocks to build, CLI commands like ivorie list and ivorie diff, and docs search. Read CONTRIBUTING.md, run npm install && npm run check, and you're set.

If you try it, tell me what broke or what you missed. Issues are the most useful thing you can give a new library. If it saves you time, a star on GitHub helps other Angular devs find it.

Thanks for reading.