BareDom v2.0.0: Zero Framework Tax UI Library

A button renders. No React baggage. No Vue overhead. Just BareDom v2.0.0, mocking the framework circus.

BareDom v2.0.0: 80 Components That Spit in Frameworks' Faces — theAIcatchup

Key Takeaways

  • BareDom v2.0.0 delivers 80 responsive components with zero runtime framework overhead.
  • x-theme engine offers 8 presets and easy custom theming via design tokens.
  • Built on Custom Elements and Shadow DOM for lightweight, standards-first UIs.

BareDom v2.0.0 exists.

And it’s better than you think — or at least, better than most framework slop we’ve endured lately.

Look, in a world drowning in React clones and Tailwind bloat, this ClojureScript oddball promises zero framework tax. Eighty components. Custom themes. Fully responsive. The dev, avanelsas, calls it the biggest update yet. Skeptical? Me too. But let’s poke it.

I’ve just released BareDom v2.0.0, and it’s the biggest update yet. BareDom has always been about “No framework, just the DOM,” but v2.0.0 brings the library into a new form: a fully responsive design system powered by a centralized theming engine.

That’s straight from the announcement. Punchy. Honest. No vaporware vibes here.

Why BareDom v2.0.0 Feels Like a Middle Finger to Frameworks?

Frameworks. They’re everywhere — bloated, opinionated, slowing your site to a crawl. BareDom? Nope. It’s Custom Elements v1 and Shadow DOM. Tree-shakeable ES modules from Google Closure. Your button doesn’t drag in a 500KB runtime.

Mobile-first now, too. All 80 components reworked. Demos flex on phones without choking. Spacing tweaks. Interaction states that don’t feel like 2012 Android.

Here’s the killer: x-theme. One component rules them all. No CSS var scavenger hunts. Thirty-three design tokens for type, space, shadows, colors. Eight presets — ocean, forest, sunset, neo-brutalist (yes, really), aurora, mono-ai, warm-mineral, default.

registerPreset() lets you mash your own. Partial merging. Brand it silly.

Setup? Laughably simple:

Hello BareDom v2

Import. Init. Done. No webpack wrestling.

But wait — is this just another toy? Nah. Eighty components. Buttons to complex layouts. All themed. All responsive. Demos updated with a picker. Poke around on GitHub or the live page.

Does BareDom v2.0.0 Actually Beat Tailwind or Headless UI?

Short answer: In niches, yes.

Tailwind’s great — until your CSS balloons. Headless UI? Solid, but React-locked. BareDom’s vanilla. PWA dreams. Static sites. Anywhere frameworks feel heavy.

Dry humor alert: It’s like finding a flip phone in 2024. Basic. Reliable. Battery lasts forever (metaphorically, your bundle size).

Unique insight time — and here’s one the announcement skips: This echoes the post-jQuery vanilla JS renaissance around 2015. Remember when we ditched $() for querySelectorAll? BareDom’s that for components. Bold prediction: In the Tauri/Electron bloat era, it’ll carve a niche for desktop PWAs. No Node runtime tax. Just DOM. Watch indie game devs or dashboard nerds flock.

Critique the spin? The “zero framework tax” claim holds — but ClojureScript compile? Niche appeal. If you’re JS purist, fine. Others might blink at the stack.

Presets shine, though. Neo-brutalist? Edgy. Mono-ai? Terminal chic. Sunset? Warm glow without Instagram filter cringe. Pick your poison — dev asks for faves. Mine’s aurora. Glowy without trying.

The Guts: What Makes It Tick?

Stack breakdown. ClojureScript to ES modules. Tiny. No deps. Standards-compliant.

Components modular. Import x-button? That’s it. No bundle surprise.

Theming centralizes chaos. One x-theme wrapper. Cascades everywhere. Responsive? Media queries baked in, smart-like.

Demos? Eighty pages. All picker-enabled. Mobile testable. Feels pro.

Wander a bit: Ever built a button lib? Pain. Shadows wrong. Hover jank. BareDom nails it. Consistent. Performant.

But — em-dash aside — will corps adopt? Doubtful. React inertia’s real. This is for rebels. Solo devs. Open-source purists.

BareDom v2.0.0’s Weak Spots (Because Balance)

Single sentence paragraph.

Not perfect. Docs? GitHub thin. No TypeScript out-the-box (yet?). Presets pretty, but roll your own scales with team handoff? We’ll see.

PR spin check: “High-performance, beautiful UIs.” Bold. Demos back it. But beauty’s subjective — neo-brutalist ain’t for suits.

Still, zero runtime? Gold in ad-blocker hell.

Why Should You Care, Dev?

Burned by Next.js hydration? Here.

Static site gen? Here.

Micro-frontends without madness? Here.

It’s not replacing Shadcn/UI tomorrow. But for greenfield, prototype, or perf audit — grab it.

GitHub: avanelsas/baredom. Demos live. Fork. Theme. Ship.


🧬 Related Insights

Frequently Asked Questions

What is BareDom v2.0.0?

Eighty responsive UI components. No frameworks. Themed via x-theme. ClojureScript to tiny modules.

Does BareDom v2.0.0 work on mobile?

Yes. All components overhauled. Demos responsive. Touch-friendly.

Best BareDom v2 presets?

Neo-brutalist for edge. Aurora for glow. Try the picker.

Priya Sundaram
Written by

Hardware and infrastructure reporter. Tracks GPU wars, chip design, and the compute economy.

Frequently asked questions

What is BareDom v2.0.0?
Eighty <a href="/tag/responsive-ui/">responsive UI</a> components. No frameworks. Themed via x-theme. ClojureScript to tiny modules.
Does BareDom v2.0.0 work on mobile?
Yes. All components overhauled. Demos responsive. Touch-friendly.
Best BareDom v2 presets?
Neo-brutalist for edge. Aurora for glow. Try the picker.

Worth sharing?

Get the best AI stories of the week in your inbox — no noise, no spam.

Originally reported by Dev.to

Stay in the loop

The week's most important stories from theAIcatchup, delivered once a week.