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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@titanom/css2tailwind

v0.1.5

Published

A tool for compiling css files to CssInJs objects to be used inside tailwindcss plugins.

Downloads

6

Readme

@titanom/css2tailwind

A tool for compiling css files to CssInJs objects to be used inside tailwindcss plugins.

Installation

pnpm add -D @titanom/css2tailwind

Setup

Add following scripts to your package.json.

{
  "scripts": {
    "styles:build": "css2tailwind src/styles .styles",
    "styles:watch": "css2tailwind src/styles .styles --watch"
  }
}

[!WARNING] If you are type-checking tailwind.config.ts, make sure to build the styles before.

Edit your tailwind.config.ts.

import plugin from 'tailwindcss/plugin.js';

import base from './.styles/base.json';
import utilities from './.styles/utilities.json';
import components from './.styles/components.json';

import type { Config } from 'tailwindcss';

const config = {
  plugins: [
    plugin(
      ({ addComponents, addUtilities, addBase }) => {
        addBase(base);
        addUtilities(utilities);
        addComponents(components);
      },
    ),
  ],
} satisfies Config;

export default config;

Edit your .gitignore.

.styles

Start adding your styles.
All styles within a directory nested in the styles-directory will be compiled into a json file with the same name.
It is required to nest individual css files in a directory having the same name. This encourages colocating documentation with the corresponding styles .e.g using storybook.

/* src/styles/components/button/button.css */
.button {
  &-primary {
    @apply bg-blue-400;
  }
}

/* src/styles/components/tag/tag.css */
.tag {
  @apply p-4;
}

/* src/styles/utilities/content/content.css */
.content-auto {
  content-visibility: auto;
}

.content-hidden {
  content-visibility: hidden;
}

/* src/styles/base/typography/typography.css */
h1 {
  @apply font-bold;
}

This will compile into the following output (formatted):

// .styles/components.json
{
  ".button-primary": {
    "--tw-bg-opacity": "1",
    "backgroundColor": "rgb(96 165 250 / var(--tw-bg-opacity))"
  },
  ".tag": { "padding": "1rem" }
}

// .styles/utilities.json
{
  ".content-auto": { "contentVisibility": "auto" },
  ".content-hidden": { "contentVisibility": "hidden" }
}

// .styles/base.json
{ "h1": { "fontWeight": 700 } }

Including other Styles

To include styles defined in your custom css files inside other css files, you must use the @import directive.

/* src/styles/utilities/content/content.css */
.content-auto {
  content-visibility: auto;
}

/* src/styles/components/button/button.css */
@import "utilities/content";

.button {
  @apply content-auto;
}

Usage

CLI

$ css2tailwind --help

css2tailwind <styles-directory> <output-directory>

Positionals:
  styles-directory  path to the source styles directory                 [string]
  output-directory  path to the output file                             [string]

Options:
      --version  Show version number                                   [boolean]
  -w, --watch    Watch for file changes               [boolean] [default: false]
  -c, --config   Path to the tailwind configuration file
                                        [string] [default: "tailwind.config.ts"]
  -h, --help     Show help                                             [boolean]