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

@teams4soft/teams4soft-ui

v0.2.0

Published

Librería de componentes UI de Teams4Soft: React + TypeScript, tematizable y accesible.

Readme

@teams4soft/teams4soft-ui

Librería de componentes UI de Teams4Soft: React + TypeScript, tematizable, accesible y neutra.

Instalación

pnpm add @teams4soft/teams4soft-ui

Importa los estilos una vez en el punto de entrada de tu app:

import "@teams4soft/teams4soft-ui/styles.css";

Peer dependencies (Radix)

Algunos componentes usan primitivas de Radix UI como peer dependencies — no se instalan automáticamente, tu proyecto debe declararlas:

  • Tooltip requiere @radix-ui/react-tooltip.
  • CheckboxField requiere @radix-ui/react-checkbox.
  • RadioGroup requiere @radix-ui/react-radio-group.
  • Los componentes con soporte asChild (composición vía Slot, p. ej. Button) requieren @radix-ui/react-slot.
pnpm add @radix-ui/react-slot @radix-ui/react-tooltip @radix-ui/react-checkbox @radix-ui/react-radio-group

Componentes disponibles

Importables desde el paquete raíz (@teams4soft/teams4soft-ui) o desde los subpaths @teams4soft/teams4soft-ui/primitives, @teams4soft/teams4soft-ui/forms y @teams4soft/teams4soft-ui/layout:

  • Button (primitives) — botón con variantes, tamaños, estado loading y soporte asChild.
  • Tooltip / TooltipProvider (primitives) — tooltip accesible sobre @radix-ui/react-tooltip.
  • FormField (forms) — wiring de accesibilidad (label, descripción, error) para controles de formulario.
  • TextField (forms) — campo de texto controlado/no controlado, con soporte de clear, password y loading, integrado con FormField.
  • CheckboxField (forms) — control booleano/indeterminado con label, descripción y error, sobre Radix Checkbox.
  • RadioGroup (forms) — selección única de un conjunto de opciones, sobre Radix RadioGroup.
  • Fieldset (layout) — agrupación semántica nativa de controles relacionados, sobre <fieldset>/<legend>.
  • FormGrid / FormGrid.Item (layout) — grid responsivo para formularios, construido sobre CSS Grid + Tailwind.

Fase 2a: ejemplos mínimos

import { CheckboxField, FormField, RadioGroup, TextField } from "@teams4soft/teams4soft-ui/forms";
import { Fieldset, FormGrid } from "@teams4soft/teams4soft-ui/layout";

// CheckboxField
<CheckboxField
  label="Acepto los términos"
  checked={accepted}
  onCheckedChange={(next) => setAccepted(next === true)}
/>;

// RadioGroup
<RadioGroup
  label="Plan"
  value={plan}
  onValueChange={setPlan}
  options={[
    { value: "basic", label: "Básico" },
    { value: "pro", label: "Pro" },
  ]}
/>;

// Fieldset (TextField no tiene prop `label`: se etiqueta envolviéndolo en FormField)
<Fieldset legend="Datos de contacto" description="Usamos esto solo para notificarte">
  <FormField label="Email">
    <TextField type="email" />
  </FormField>
</Fieldset>;

// FormGrid
<FormGrid columns={{ base: 1, md: 2 }} gap="md">
  <FormGrid.Item span={{ base: 1, md: 2 }}>
    <FormField label="Nombre completo">
      <TextField />
    </FormField>
  </FormGrid.Item>
  <FormField label="Ciudad">
    <TextField />
  </FormField>
</FormGrid>;

Utilidades

  • cn(...classes) — combina clases y resuelve conflictos de Tailwind (las últimas ganan).
  • composeEventHandlers(theirs, ours) — compone handlers respetando preventDefault.
  • mergeRefs(...refs) — combina varias refs en una.

Estado

En construcción por fases.

Publicación (mantenedores)

  1. Crear NPM_TOKEN (token de automatización con 2FA) en la organización @teams4soft y guardarlo como secret del repo.
  2. Subir un tag y crear un GitHub Release → el workflow release.yml publica con provenance.