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

@one-nexty/tailwind-config

v0.2.0

Published

Adaptateur web : traduit @one-nexty/tokens en thème Tailwind CSS v4 (@theme) + preset JS de compatibilité.

Readme

@one-nexty/tailwind-config

Adaptateur web du design system : traduit @one-nexty/tokens en thème Tailwind CSS v4.

C'est une couche jetable. Le jour où l'on change de moteur CSS, on remplace ce package — les tokens, eux, ne bougent pas.

Utilisation (Tailwind v4 — chemin principal)

@import "tailwindcss";
@import "@one-nexty/tailwind-config/theme.css";

Cet import apporte :

  • la palette primitive dans un bloc @themebg-primary-500, p-4, rounded-lg… ;
  • les tokens sémantiques dans un bloc @theme inlinebg-surface, text-fg-muted, border-border, ring-ring… ;
  • les valeurs clair/sombre de ces tokens (:root et .dark) ;
  • la variante dark: pilotée par la classe .dark sur <html> ;
  • une couche de base commune (fond, couleur de texte, police, focus visible).

Pourquoi deux blocs @theme ?

| Bloc | Contenu | Comportement | | --------------- | --------------------- | ---------------------------------------------------------------------------------------------- | | @theme | Palette primitive | Valeurs littérales. bg-primary-500 vaut #635BFF en clair comme en sombre. | | @theme inline | Tokens sémantiques | bg-surface compile en var(--nx-color-surface). La bascule de thème se fait à l'exécution. |

Sans inline, Tailwind figerait la valeur au moment de la compilation et le thème sombre demanderait un second passage de build.

Preset JavaScript (secondaire)

index.js expose le même thème sous forme d'objet { theme: { extend: … } }, construit dynamiquement depuis @one-nexty/tokens. Il sert aux consommateurs qui ne lisent pas de CSS :

// App encore en Tailwind v3
import preset from "@one-nexty/tailwind-config";
export default { presets: [preset], content: ["./src/**/*.tsx"] };
// Outillage : générateur de doc, export Figma, thème React Native
import { colors } from "@one-nexty/tailwind-config";

Régénérer

pnpm --filter @one-nexty/tailwind-config build   # lit @one-nexty/tokens → dist/theme.css

dist/ est gitignoré. Il dépend de @one-nexty/tokens : pnpm -r build garantit le bon ordre.