Zero Config · Zero FOUC · Zero Runtime · Build-Time CSS-in-JS
English | 한국어
Devup UI isn't just another CSS-in-JS library — it's the next evolution.
Traditional CSS-in-JS solutions force you to choose between developer experience and performance. Devup UI eliminates this trade-off entirely by processing all styles at build time using a Rust-powered preprocessor.
- Broad Syntax Coverage: Variables, conditionals, responsive arrays, pseudo-selectors,
styled(), Emotion'scssprop and more compile at build time; anything the build cannot know is a located build error, never a silent miss (supported syntax & limitations) - Familiar API:
styled()API compatible with styled-components and Emotion patterns - True Zero Runtime: No JavaScript execution for styling at runtime. Period.
- Smallest Bundle Size: Optimized class names (
a,b, ...aa,ab) minimize CSS output - Fastest Build Times: Rust + WebAssembly delivers unmatched preprocessing speed
npm install @devup-ui/react
# on next.js
npm install @devup-ui/next-plugin
# on vite
npm install @devup-ui/vite-plugin
# on rsbuild
npm install @devup-ui/rsbuild-plugin
# on webpack
npm install @devup-ui/webpack-plugin- Preprocessor — All CSS extraction happens at build time
- Zero Config — Works out of the box with sensible defaults
- Zero FOUC — No flash of unstyled content, no Provider required
- Zero Runtime — No client-side JavaScript for styling
- RSC Support — Full React Server Components compatibility
- Library Mode — Build component libraries with extracted styles
- Dynamic Themes — Zero-cost theme switching via CSS variables
- Type-Safe Themes — Full TypeScript support for theme tokens
- Smallest & Fastest — Proven by benchmarks
Latest CI benchmark (commit 3594eb3b, Devup UI 1.0.44, 2026-11-19) on ubuntu-26.04 with Next.js 16.4.6. Every row is the median of 3 cold builds that ran in rotating order, shown with the range of the samples. All Next.js builds use the native TypeScript 7 CLI for type checking. The English and Korean tables are generated from the same checked result file, benchmark-results.json, which CI refreshes after every merge to main and records in benchmark/history.json, one entry per commit, so a slower build can be traced to the merge that caused it.
Client Size is the JavaScript and CSS shipped to the browser, uncompressed: .next/static/**/*.{js,css} or vinext dist/client/**/*.{js,css}. Build Size is the deployable build output, uncompressed: what a deployment uploads, never the caches and type-check files a build leaves next to it. For Next.js it is .next without cache/ (the Webpack/Turbopack and SWC caches and TypeScript's .tsbuildinfo), Turbopack's build-time build/, the generated types/, diagnostics/, the trace files, the output-tracing *.nft.json records and source maps, which is about what Next.js's output: 'standalone' copies plus .next/static; for vinext it is dist without source maps. The rule is isDeployed in benchmark-output.js; history entries recorded before it (no bytesDefinition in benchmark/history.json) counted the whole output directory. CSS Size counts only browser-shipped CSS: .next/static/**/*.css (Webpack static/css and Turbopack static/chunks) or vinext dist/client/**/*.css, excluding caches and server CSS. A missing browser-assets directory is an error; an existing directory with no CSS counts zero. Every size is measured on every sample and shown as the median; benchmark-results.json keeps the samples with their range, and rows measured before Client Size was recorded show n/a. Approved CSS measurement corrections are limited to explicitly named devup-ui, devup-ui-single and vinext-devup-ui rows. bun benchmark-check.js --write-css-baseline devup-ui retains the per-file mode; bun benchmark-check.js --write-css-baseline devup-ui-single,vinext-devup-ui selects only the other two rows in one comma-separated argument. Only selected existing rows' CSS bytes change; unlike --write-baseline, this preserves sample count, build bytes, ratios, tolerances, all unselected rows and calibration history. Missing or unsupported names and conflicting writer modes are rejected.
Webpack:
| Library | Version | Median Build Time | Range | Client Size | Build Size | CSS Size |
|---|---|---|---|---|---|---|
| tailwindcss | 4.3.5 | 10.19s | 10.09s - 10.52s | 924,205 bytes | 1,796,355 bytes | 717 bytes |
| styleX | 0.19.2 | 21.87s | 21.80s - 22.19s | 2,021,495 bytes | 2,828,421 bytes | 661 bytes |
| vanilla-extract | 1.21.3 | 9.23s | 9.18s - 9.45s | 923,744 bytes | 1,795,160 bytes | 398 bytes |
| kuma-ui | 1.6.4 | 10.69s | 10.35s - 10.69s | 956,179 bytes | 1,858,609 bytes | 354 bytes |
| panda-css | 2.5.0 | 10.65s | 10.48s - 10.68s | 980,304 bytes | 1,890,730 bytes | 18,567 bytes |
| chakra-ui | 3.38.0 | 16.43s | 16.22s - 16.56s | 1,175,920 bytes | 2,441,133 bytes | 0 bytes |
| mui | 9.5.0 | 11.53s | 11.38s - 11.55s | 993,420 bytes | 1,934,375 bytes | 0 bytes |
| devup-ui (per-file CSS) | 1.0.44 | 8.92s | 8.91s - 9.03s | 923,709 bytes | 1,793,372 bytes | 325 bytes |
| devup-ui (single CSS) | 1.0.44 | 8.96s | 8.81s - 9.01s | 923,709 bytes | 1,793,540 bytes | 325 bytes |
Turbopack:
| Library | Version | Median Build Time | Range | Client Size | Build Size | CSS Size |
|---|---|---|---|---|---|---|
| tailwindcss | 4.3.5 | 3.91s | 3.87s - 3.92s | 571,690 bytes | 1,368,423 bytes | 653 bytes |
| devup-ui (direct APIs, single CSS) | 1.0.44 | 3.87s | 3.84s - 3.88s | 571,186 bytes | 1,366,865 bytes | 325 bytes |
devup-ui (static .css.ts) |
1.0.44 | 3.85s | 3.79s - 3.89s | 571,283 bytes | 1,367,113 bytes | 376 bytes |
The Turbopack ranges overlap, so the direct-API median is 0.03s (0.8%) ahead of Tailwind on this fixture and the two are effectively at parity. The 3 cold samples were Tailwind 3.92s, 3.87s, 3.91s, direct Devup UI 3.84s, 3.87s, 3.88s, and static .css.ts 3.89s, 3.79s, 3.85s. The fixtures have comparable app shapes, not pixel-identical styling: Tailwind styles the leading paragraph and button more heavily, while Devup UI exercises typed component/style props. Treat these as build-pipeline results rather than a per-rule microbenchmark. Every .css.ts module runs on the full Boa evaluator, which adds about 20 ms for the first module and under 1 ms for each further one. CI compares the Devup UI rows with a checked baseline (see benchmark-gate.js for the rule) and fails on a regression beyond the measured noise.
Devup UI transforms your components at build time. Class names are generated using a compact base-37 encoding for minimal CSS size.
Basic transformation:
Generated class and CSS variable names may change between versions, build state, and prefix settings; do not manually reuse them.
You write:
import { Box } from '@devup-ui/react'
const example = <Box _hover={{ bg: 'blue' }} bg="red" p={4} />Devup UI generates:
import "@devup-ui/react/devup-ui.css";
const example = <div className="a b c" />;With CSS:
/*! devup-ui v1.0.82 | Apache License 2.0 | https://devup-ui.com */.b{background:red}.c{padding:16px}.a:hover{background:blue}Dynamic values become CSS variables:
You write:
import { Box } from '@devup-ui/react'
const example = <Box bg={colorVariable} />Devup UI generates:
import "@devup-ui/react/devup-ui.css";
const example = <div className="a" style={{ "--b": colorVariable }} />;With CSS:
/*! devup-ui v1.0.82 | Apache License 2.0 | https://devup-ui.com */.a{background:var(--b)}Complex expressions and responsive arrays:
You write:
import { Box } from '@devup-ui/react'
const example = <Box bg={['red', 'blue', isActive ? 'green' : dynamicColor]} />Devup UI generates:
import "@devup-ui/react/devup-ui.css";
const example = <div className={`a b ${isActive ? "c" : "d"}`} style={{ "--e": dynamicColor }} />;With responsive CSS for each breakpoint:
/*! devup-ui v1.0.82 | Apache License 2.0 | https://devup-ui.com */.a{background:red}@media(min-width:480px){.b{background:blue}}@media(min-width:768px){.c{background:green}.d{background:var(--e)}}Type-safe theming:
devup.json
{
"theme": {
"colors": {
"default": {
"primary": "#0070f3",
"text": "#000"
},
"dark": {
"primary": "#3291ff",
"text": "#fff"
}
},
"typography": {
"heading": {
"fontFamily": "Pretendard",
"fontSize": "24px",
"fontWeight": 700,
"lineHeight": 1.3
}
}
}
}// Type-safe theme tokens
const textExample = <Text color="$primary" />
const boxExample = <Box typography="heading" />Custom shorthands:
Define reusable prop aliases in the build plugin options. Property names may use camelCase or CSS kebab-case, and one shorthand can target multiple properties.
// vite.config.ts
export default defineConfig({
plugins: [
DevupUI({
shorthands: {
insetX: ['left', 'right'],
scrollMarginX: ['scrollMarginLeft', 'scrollMarginRight'],
},
}),
],
})The plugin adds configured names to the generated declaration file, so they are
available as type-safe component props and selector properties after the plugin
has run. Restart the build after changing this option so df/theme.d.ts is
regenerated. The same value is applied to every target property.
If your tsconfig.json limits include to src, also include df/*.d.ts (or
the matching custom distDir) so the generated augmentation is loaded.
const pinned = <Box insetX={0} />
const responsive = <Box insetX={[0, null, 'auto']} />
const interactive = <Box _hover={{ insetX: 4 }} />Responsive + Pseudo selectors together:
// Responsive with pseudo selector
const example = <Box _hover={{ bg: ['red', 'blue'] }} />
// Equivalent syntax
const example2 = <Box _hover={[{ bg: 'red' }, { bg: 'blue' }]} />styled-components / Emotion compatible styled() API:
import { styled } from '@devup-ui/react'
// Familiar syntax for styled-components and Emotion users
const Card = styled('div', {
bg: 'white',
p: 4, // 4 * 4 = 16px
borderRadius: '8px',
boxShadow: '0 4px 6px rgba(0, 0, 0, 0.1)',
_hover: {
boxShadow: '0 10px 15px rgba(0, 0, 0, 0.1)',
},
})
const Button = styled('button', {
px: 4, // 4 * 4 = 16px
py: 2, // 2 * 4 = 8px
borderRadius: '4px',
cursor: 'pointer',
})
// Usage
const cardExample = <Card>Content</Card>
const buttonExample = <Button>Click me</Button>- Styled System
- Chakra UI
- Theme UI
- Vanilla Extract
- Rainbow Sprinkles
- Kuma UI
To set up the development environment, install the following packages:
bun install
bun run build
cargo install cargo-tarpaulin
cargo install wasm-packAfter installation, run bun run test to ensure everything works correctly.