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

@quarks-css/quarks

v1.0.0

Published

A CSS-in-JS library for applying styles to React components via props

Downloads

2

Readme

WIP

This project is in active development

Quarks

What are quarks?

Quarks are React components, but with all valid CSS properties available as props. They use Goober to inject styles either statically or dynamically as needed.

Why quarks?

1. Enforce syntax and types via Typescript 🤓

  • Many CSS-in-JS libraries rely on tagged template literals to create component styles, sometimes offering object syntax as an alternative. However, template literals forego the benefits of Typescript since the contents of template literals are not evaluated. This allows for mistakes to go unchecked. With Quarks type-safety is always enforced.

2. Directly referenced theme values

  • Most CSS-in-JS libraries provide access to a theme via a prop argument in a callback. But lazy or inexperienced developers usually don't take advantage of that and instead either import theme values or hard-code style values because it's easier 😱. One of quarks' main goals is to make referencing theme values easier than hard-coding styles, ensuring that your application's theme is consistently followed and easy to change.

3. Easily apply conditional styling

  • Nearly all CSS-in-JS libraries allow for conditional styling via custom props. Having to name and keep track of all of these props is a needless hassle that leads to poor naming and confusing code 🍝. Since your components' state, props, or other variables are already available to quarks via props, this is never a problem.

4. Avoid convoluted component names

  • Most CSS-in-JS libraries require each styled element to be declared as a separate React component. That means having to come up with (yet another) descriptive name for every element. This wastes time and can lead to confusion when elements inevitably have similar or convoluted names. Since each quark is only unique in its element tag name, it's always clear what each quark represents and there's never a need to spend time trying to uniquely name them.

Why "quarks"?

It's a reference to Brad Frost's Atomic Design Methodology. If atoms are your smallest design element that make up buttons, icons, text, etc., then what make up atoms? Quarks of course!

Authors