Files
zeekayandHanzo Dev c79181b3bf types: TypeScript 7 native for the 18 packages where it agrees with tsc
Adds @typescript/native-preview (tsgo 7.0.0-dev.20260707.2) and points
`typecheck`/`tc` at it wherever the Go compiler was verified to reach the same
verdict as tsc. Measured, package by package, both compilers on the same
invocation:

  agree, green (18)   pkg/ui, pkg/data, annotate, canvas, cd, dashboard,
                      observe, observe-native, observe-svelte, products, react,
                      tests, agent-ui, commerce, checkout, apps/cd
  tsgo disagrees (2)  event  — TS2345 on Uint8Array<ArrayBufferLike> vs
                               ArrayBufferView<ArrayBuffer> in src/uid.ts:34
                      shop   — TS2591, does not pick up the node globals tsc
                               resolves for components/PaymentStep.tsx
  red under both (3)  shadcn, @hanzo/ui-web, v4 — pre-existing type errors,
                      left on tsc so the diff is the compiler, not the errors

event and shop stay on tsc. They are the report, not an oversight.

pkg/ui was red before this: `tsc --noEmit` failed on render.test.tsx, where
ResizablePanelGroup was written without its required `direction`. The build
never caught it because tsconfig.build.json excludes tests, so the shipped
package typechecked green in CI and red on a developer's machine. Fixed, and
pkg/ui is now green under both compilers: 21 test files, 212 tests passing.

Emit stays on tsc everywhere, deliberately. tsgo can emit pkg/ui — 920 files,
identical file list, and the only differences are comment retention in .js and
alphabetical member ordering in .d.ts, i.e. semantically equal. But this is a
published package and tsgo is a dev preview, so the artifact keeps the compiler
it has until tsgo ships stable. The flip is a one-line change when it does.

`tc` in commerce and checkout was `tsc` with no flags, against a tsconfig with
noEmit:false and declaration:true — running it emitted 188 .js/.d.ts files
directly into the source trees, next to the .ts they came from. A typecheck
script that writes build output into src is a trap; both are now `tsgo --noEmit`.

shadcn imported `type Config from "tailwindcss"` while declaring no dependency
on it, resolving through the root package.json instead. Now that the root no
longer carries Tailwind, the package declares the version it actually uses.

Verified: pnpm build → 21 successful, 21 total.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-03 18:02:20 -07:00
..

shadcn

A CLI for adding components to your project.

create

Use the create command to create a new project. You will be taken to a website to build your custom design system and choose your framework.

npx shadcn create

init

Use the init command to initialize dependencies for a new project.

The init command installs dependencies, adds the cn util, configures Tailwind CSS, and CSS variables for the project.

npx shadcn init

add

Use the add command to add components to your project.

The add command adds a component to your project and installs all required dependencies.

npx shadcn add [component]

Example

npx shadcn add alert-dialog

You can also run the command without any arguments to view a list of all available components:

npx shadcn add

Documentation

Visit https://ui.shadcn.com/docs/cli to view the documentation.

License

Licensed under the MIT license.