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

@keboola/tailwind-config

v2.0.0

Published

Shared Tailwind CSS v4 design tokens for the Keboola UI platform — semantic color palette, type scale, radii and shadows as a `theme` object.

Readme

@keboola/tailwind-config

Shared Tailwind CSS design tokens for the Keboola UI platform — the same semantic color palette, type scale, radii and shadows that @keboola/design is built on, shaped as a Tailwind theme object.

Use this when you want your Tailwind-styled app to inherit the platform's visual primitives — most relevant for audiences B (Keboola-branded external builders) and audience A (internal monorepo work). Audience C (customer- branded) typically supplies its own tokens; this package is optional then.

Install

npm install -D @keboola/tailwind-config tailwindcss@^4
# or
pnpm add -D @keboola/tailwind-config tailwindcss@^4

Tailwind v3 is no longer supported — stay on @keboola/[email protected] if you need it.

Use

The package exports tokens only: { theme }. Everything a v4 build owns in CSS — the class prefix, the @imported layers, preflight, plugins — belongs in your stylesheet, not in this object.

Load it through v4's @config bridge from your own tailwind.config.{js,ts}:

import keboolaConfig from '@keboola/tailwind-config';

export default {
  theme: keboolaConfig.theme,
  plugins: [
    /* your own plugins */
  ],
};
/* styles.css */
@import 'tailwindcss/theme.css' layer(theme) prefix(tw);
@import 'tailwindcss/utilities.css' layer(utilities) prefix(tw);
@config './tailwind.config.js';

Class prefix (tw- in v3, tw: in v4)

@keboola/design components ship with prefixed class names baked into their compiled JS, and those classes only render if a stylesheet the app loads actually defines them. In v4 the prefix is declared in CSS (prefix(tw) on the @import, producing tw:flex), not in this config — so whether you can drop it depends on how you load design's stylesheet:

  1. Build-from-source (the monorepo / apps/boilerplate pattern) — the app imports the source stylesheet @keboola/design/styles and runs its own Tailwind pass over design's dist/ plus its own markup. That pass emits the components' classes using your prefix, so dropping prefix(tw) renders design components UNSTYLED. Keep the prefix for build-from-source setups.

  2. Precompiled CSS — the app imports @keboola/design/styles/compiled (the shipped dist/styles.css, which already contains every prefixed utility the components use, prebuilt). Design components are then styled by that stylesheet regardless of your own prefix, so authoring your utilities unprefixed is safe: design's classes and yours live in the same cascade without colliding.

Bottom line: prefix-less is safe only when you consume design via /styles/compiled, not when you build design's utilities from source.

Subpath imports

If you only need the raw token data:

import colors from '@keboola/tailwind-config/colors';
import typography from '@keboola/tailwind-config/typography';

Heads up — colors and typography are shipped as .ts source. Resolution works when the consumer loads the config through Tailwind (which uses jiti under the hood) or any bundler that's TypeScript-aware (Vite, esbuild, swc, tsx, ts-node via --loader). Plain Node ESM cannot load these files without a TS loader. A pre-compiled .js variant is planned — track or open an issue if your toolchain hits this.

Layout

  • index.js — the token entry ({ theme }); consumed via import (ESM).
  • colors.ts — semantic palette (primary, background, foreground, muted, border, destructive, etc.) wired to the CSS variables shipped by @keboola/design.
  • typography.ts — typography scale (used by the @tailwindcss/typography plugin, which you install and register yourself).
  • scrollFade.ts — optional scroll-fade utility plugin.

Plugins

Earlier versions bundled tailwindcss-animate, @tailwindcss/typography, @tailwindcss/container-queries and tailwindcss-scoped-preflight and registered them for you. They are gone: in v4 container queries are core, animations come from tw-animate-css, and preflight scoping is a @plugin directive in CSS. Register whatever you still need in your own config — @keboola/design's tailwind.config.js and styles.css are the reference setup.

License

MIT