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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@ferments/css

v0.0.1-alpha.3

Published

Contains the source for the css library

Downloads

11

Readme

Ferments.css

The css files that make up Declare.css.

Exceptions:

  • font-style has acronym fi, since fs is for the more common font-size
  • overflow has acronym of, as opacity uses o
  • position names are just the values (i.e. relative instead of p-r), which frees up p for padding
  • min and max widths and heights are minw/maxw/minh/maxh so they don't collide with m for margin
  • basic text styling has shortcuts i and b for italic and bold (but prefer <strong> and <emphasis> tags for semantics, when appropriate)

CSS tips

  • use semantic HTML tags or apply aria attributes
  • ideally only use .class, [attribute], and :pseudo selectors to keep specificity low
  • don't set a font size on the body (allows the user to set one they like), and all other text should use rem units
  • flex should be your default positioning system, and grid should be used for layouts (adhoc rather than a framework)
  • use margins for fine-tuning layout between elements, and padding for within an element
  • prefer an inline-block with flex's justify-content rather than text-align... it works better with different browsers/language directions
  • if you don't like the default outline, replace it, never just remove it
  • :hover and :focus should nearly always do the same thing (hence the --P for pin), but remember to use :active for things like a button press
  • only use opacity for a fade effect
  • transition/animations should really only use opacity and transform for speed and to not cause re-layouts

TODO

  • [ ] generate index.css files depending on inclusions and bundling
  • [x] postcss-replace from a config file
  • [ ] replace increments with more descriptive titles (i.e. timing-1 with timing-xs, media-6 with media-xxl, etc.)?
  • [ ] replace zeros with actual property value (i.e. visibility-0 with visibility-none, etc)?
  • [ ] optional typography override?
  • [ ] optional complement theme?
  • [ ] optional components?
  • [ ] eject option?