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

flexbox-classes

v2.2.1

Published

Minimal, low-level set of CSS classes for flexbox

Readme

flexbox-classes

Simplest-ever CSS classes for flexbox based layout with notes willfully copied from MDN pages. Class names are loosely based on the SUIT CSS naming convention, but purists may have concerns.

##TL;DR

###Install

npm i flexbox-classes

###Use

With webpack, configure your css-loader

module: {
		loaders: [
			{
				test: /\.css$/,
				loader: "style-loader!css-loader"
			},
			//...
			]
			//...
			

, then in your code:

require('flexbox-classes');

With any other tool, just link or import

node_modules/flexbox-classes/css/[email protected]

Version

Is the flexbox model confusing?

No, not really. But when you're just starting to use it, the similarity of terms can be an impediment to getting your head around it.

Are there learning resources out there?

Absolutely. Many, many good ones exist including MDN. Just google.

Then why?

Easy. When you are old-school, it helps to go through each property and option and see how it fits into the big picture. Then it made sense to 'document' some things in a LESS file that I could use on projects.

Things that could be better emphasized in tutorials

Flexbox containers and flexbox items.

These are two different roles that any item (element) may serve in the context of the flexbox model. A flexbox-container is simply an element that lays out its children using the model. A flexbox-item is simply a child on a flexbox-container.

Of course, other flexbox properties can be applied to either the parent and/or the children to impact their display behavior.

In some cases, an element will serves one role, in other cases, it may serve the other role. And there is nothing that prevents an element from being both a container and item at the same time.

Flexbox properties relate to only one role.

The CSS properties that comprise the flexbox model are relevant to one and only one "role" in the sense I'm using above. For example, the property align-items only makes sense in the realm of flex-containers while the property align-self only makes sense in the realm of flex-items.

On the interwebs, I found many tutorials that descrine them in a sort of all-together style. Not sure why this is, and I should point out that not everybody does this. For example, CSS-Tricks' guide makes the distinction very well. I just find the layout of the info hard to work with.

Should I use this?

Seriously -- you're asking?

For learners, check out the simple guide in the handouts folder. We can't take much credit for it; another expert developed most of the content. We added a few remarks and made it more "page" oriented". (Thanks, Joni!)