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

@quarkcss/core

v0.5.4

Published

<!-- omit from toc --> ## Table of Contents - [Introduction](#introduction) - [Install](#install) - [Introduction](#introduction-1) - [Usage](#usage) - [Typescript](#typescript) - [Caveats](#caveats)

Downloads

37

Readme

Table of Contents

Introduction

I ❤️ stitches && ❤️ tailwind

What if stitches + tailwind = 👶?

  • Create fully-typed React styled components using atomic css classes.
  • Organize your atomic css with variants props
  • Declare default props for your base component
  • Polymorphic and composable. Reuse quark styles from one component to another.

Use with your favorite atomic css library:

For framerwork-agnostic styling, use @quarkcss/core

Install

npm install @quarkcss/core

pnpm install @quarkcss/core

yarn add @quarkcss/core

| Package | Minified | Gzipped | | ----------------- | -------- | ------- | | @quarkcss/core | 1.02KB | 0.54KB | | @quarkcss/react | 1.09KB | 0.55KB |

Introduction

Fully typed framework-agnostic generator for atomic css classes.

Inspired by @stitches/core variants api to generate atomic css classes

Use with your favorite atomic css library:

For React styling, use @quarkcss/react

Usage

import { css } from '@quarkcss/core'

//Basic
const button = css({
  base: 'bg-red-500',
  variants: {
    size: {
      small: 'w-4 h-4',
      medium: ['w-8', 'h-8'], //use arrays to organize multiple classes
      large: 'w-12 h-12'
    },
    color: {
      red: 'bg-red-500',
      blue: 'bg-blue-500'
    },
    //boolean variants (when `true` or `null` keys are declared, variant prop will have `true | falsey` type)
    rounded: { 
      true: 'rounded-full', //`rounded === true`
      null: 'rounded-none'  //`rounded === falsey` (undefined | false | null | 0) or undeclared
      
      //❌ false: 'rounded-none' (Since `null` encompasses `falsey` and undeclared values)

      //Define additional keys in addition to boolean keys
      small: 'rounded-sm',
      medium: 'rounded-md',
    }
  },
  //compound variants
  compound: [
    {
      size: 'small',
      color: 'red',
      value: 'border-2 border-red-500'
    },
    {
      size: 'medium',
      color: 'blue',
      value: 'border-2 border-blue-500'
    }
  ],
  //default variants
  defaults: {
    size: 'small',
    color: 'red'
  }

})

//Usage
const classnames = button({
  size: 'medium',
  color: 'blue',
  rounded: true
})
//classnames: 'bg-blue-500 w-8 h-8 rounded-full border-2 border-blue-500'

const App = () => {
  return (
    <button className={button({size: 'medium', color: 'blue', rounded: true})}>
      Click Me
    </button>
  )
}

Typescript

//Extract QuarkVariants from css generator
const button = css({ /* ... */ }})

type Variants = GetQuarkVariants<typeof button>

//Or interface version
interface Variants extends GetQuarkVariants<typeof button> {}

Caveats

  • Specificity
    • css classes are not applied based on ordering specificity (unlike css-in-js / stitches)
      • design your variants such that atomic classes do not conflict
      • if all else fails, overide with !important (i.e. "!bg-red-500")
  • Set Tailwind VSCode plugin to recognize atomic class names outside of <... className="">
    • in VSCode settings.json:
    "tailwindCSS.experimental.classRegex": ["\"([^\"]*)\"", "'([^']*)'"],
    //TODO: Need to find more surgical regex to match atomic class names in QuarkConfig