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

@toptal/picasso-tailwind

v100.0.0

Published

Picasso Tailwind configuration

Readme

picasso-tailwind

Picasso-specific Tailwind preset that contains Picasso-specific design tokens from BASE and support for Picasso usage.

The configuration has to be used with @toptal/base-tailwind preset like in the example below.

/** @type {import('tailwindcss').Config} */
module.exports = {
  presets: [
    require('@toptal/base-tailwind'),
    require('@toptal/picasso-tailwind'),
  ],
  // ...
}

Scanning Picasso's classes — Tailwind content / @source

Picasso components ship their Tailwind classes as string literals in their compiled output, so your Tailwind build must scan @toptal/picasso* for them — otherwise those utilities are never generated. This is required, not optional: a missing glob silently drops Picasso styling, including the PicassoRootNode border-box island (its descendants would fall back to the page's content-box) and the responsive spacing classes.

Add the packages to your Tailwind content (config-based setup):

const path = require('path')

/** @type {import('tailwindcss').Config} */
module.exports = {
  presets: [
    require('@toptal/base-tailwind'),
    require('@toptal/picasso-tailwind'),
  ],
  content: [
    path.join(__dirname, 'node_modules/@toptal/picasso/**/*.js'),
    path.join(__dirname, 'node_modules/@toptal/picasso-*/**/*.js'),
    // ...your own sources
  ],
}

…or declare them with @source in your entry CSS (Tailwind v4):

@source '../node_modules/@toptal/picasso/**/*.js';
@source '../node_modules/@toptal/picasso-*/**/*.js';

Adjust the path to wherever your bundler resolves @toptal/picasso* (a hoisted vs. nested node_modules layout).

Global reset — @toptal/picasso-tailwind/base

The package also ships Picasso's global CSS reset as an opt-in entry, emitted inside @layer base. Import it in your Tailwind entry CSS, after the theme import:

@layer theme, base, components;
@import 'tailwindcss/theme.css' layer(theme);
@import '@toptal/picasso-tailwind/base';
@import 'tailwindcss/utilities.css';
@config "./tailwind.config.js";

Cascade contract: because the reset is cascade-layered, all Tailwind utilities and any unlayered application CSS win over it — the reset is a baseline, never an override. The reset establishes a content-box page box model (html { box-sizing: initial } with universal inheritance); Picasso components stay border-box via the PicassoRootNode island.

Opting out: omit the import. This replaces the former <Picasso reset={false} /> provider prop, which no longer exists.