⚠️ This project is in an experimental phase. Feel welcomed to hang out with us on Discord if you like the project!
Just like shadcn/ui but for Qwik. Part of the 𝕏 stack.
The goal of this component library collection is to have the first complete, production-ready set of reusable components for Qwik applications with copy/pasting ability a la shadcn for maximum customizability.
⚠️ This is not a 100% port. Being on Qwik means that Qwikcn must use Qwik-compatible headless libraries (hi 👋 qwik-ui & modular-forms) that can have a slightly different API compared to shadcn's headless libraries (such as radix/ui or react-hook-form). As a consequence, compatibility will be set on a best-efforts basis, but I'll to keep the base design system as close as possible. You can expect 90% parity.
⚠️ Under the hood, qwikcn uses a combination of qwik-ui's headless components, qwikify$ed shadcn components, and html elements. There aren't a lot of production ready components yet in qwik-ui, so qwikcn will adopt them as they get production ready. Until then, the most complex, non-often used shadcn headless components will be qwikify$ed, even though that can decrease performance; and those likely to be reused a lot will be served as html elements, even though that might mean less accessibility.
Please read the contributing guide.
Licensed under the MIT license.
pnpm build.server
This starter site is configured to deploy to Vercel Edge Functions, which means it will be rendered at an edge location near to your users.
The adaptor will add a new vite.config.ts
within the adapters/
directory, and a new entry file will be created, such as:
└── adapters/
└── vercel-edge/
└── vite.config.ts
└── src/
└── entry.vercel-edge.tsx
Additionally, within the package.json
, the build.server
script will be updated with the Vercel Edge build.
To build the application for production, use the build
command, this command will automatically run pnpm build.server
and pnpm build.client
:
pnpm build
To deploy the application for development:
pnpm deploy
Notice that you might need a Vercel account in order to complete this step!
The project is ready to be deployed to Vercel. However, you will need to create a git repository and push the code to it.
You can deploy your site to Vercel either via a Git provider integration or through the Vercel CLI.