npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

veneerui

v0.3.0

Published

CLI to add Veneer UI theming to an existing React + Tailwind v4 app (init, add, list). For a new app, use `npm create veneerui`.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

patkelly174patkelly174

Keywords

Readme

veneerui

CLI to add Veneer UI theming to an existing React + Tailwind v4 app — it wires the tokens, the <ThemeProvider>, and the anti-flash script for you, shadcn-style (you keep your own project).

Starting a new app? Use npm create veneerui@latest instead — it scaffolds the app and runs this same wiring end-to-end.

Everything it does is also documented as manual steps, so you can always do it by hand.

npm i @offthegully/veneerui
npx veneerui init            # wire Veneer into this project
npx veneerui add switcher    # copy a ThemeSwitcher into your components
npx veneerui add fonts       # print install + imports for the built-in themes' fonts

Commands

| Command | What it does | |---|---| | veneerui init | Detect Vite/Next, add @import "@offthegully/veneerui/tokens.css" to your global stylesheet, wire the anti-flash (Vite: the veneer() plugin; Next: <AntiFlashScript/> in the layout <head>), and wrap your root in <ThemeProvider>. Patches the entry files when it recognizes their shape, else leaves that step in VENEER-SETUP.md. Idempotent; supports --dry-run. | | veneerui add <component…> | Copy UI components (and their registry dependencies) into your project. They import their logic from @offthegully/veneerui; you own and can restyle the markup. On a Next project it prepends 'use client' (RSC needs it; inert elsewhere). --force overwrites; --dir <path> sets the target. | | veneerui add fonts | Print the npm i command and exact @fontsource import lines for every family the built-in themes name, plus the font-sans footgun. Themes can only name a font — the app must load it — and the family must match exactly; this removes the guesswork. See docs/fonts.md. | | veneerui list | List the components available to add. |

Flags: --cwd <path> to target another directory, --dry-run, --force, --dir <path>.

To stop new islands from creeping back in, add eslint-plugin-veneer — the same hardcoded-color detector the conformance test uses, enforced in your editor and CI.

Components

switcher (theme dropdown; pulls in import-panel + gallery-panel), gallery-panel (grid that previews every theme and applies one on click), import-panel (drop / paste-URL validate-and-preview modal), banner (preview banner), showcase (a token-exercising demo surface). Run veneerui list for the current set.

Why components are copied, not imported

Tailwind v4 doesn't scan node_modules, so a component shipped inside a package wouldn't have its utility classes generated in your build. Copying it into your source — where Tailwind already scans — makes the classes generate and lets you restyle freely. The runtime logic still comes from the @offthegully/veneerui dependency, so there's no duplicated behavior.

veneerui init (adding Veneer to an existing app) is web-only (Vite / Next). For a new Expo (React Native) app, npm create veneerui@latest my-app -- --framework expo scaffolds and wires it through NativeWind (experimental) — see the Expo guide.

Full setup guide (Vite, Next.js, and other React + Tailwind v4 apps): Integration guide.

License

MIT