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

css-components

v0.0.0

Published

introduces the @component selector to CSS

Downloads

9

Readme

Component CSS (CCSS) Build Status

introduces the @component selector to CSS.

this was originally released as a react specific CSS preprocessor of its own, but it is being transitioned to be a generic concept

why?

as we start to develop websites in a modular way with nested components it starts to make sense to have your selectors only effect the component you're targeting, and not have to worry about naming collisions.

by using components like this

@component Example {
  width: 100%;
  height: 100%;
  .content {
    width: 100%;
  }
}

you can produce this CSS

.app-component.app-example {
  width: 100%;
  height: 100%;
}
.app-component.app-example .app-example_content {
  width: 100%;
}

DOM helpers

CCSS is meant to be used in conjunction with a DOM helper, so you don't have to manually prefix anything.

  • react?
  • ember?
  • angular?

CCSS is also meant to be used after a CSS preprocessor

  • stylus?
  • scss?
  • less?

stuff to know

if your CSS preprocessor doesn't support root properties inside of a component you can nest them inside of a self selector like this

@component Example {
  self {
    width: 100%;
    height: 100%;
  }
}

theres also the concept of states

@component Example {
	state::active {
		width: 100%;
	}

	.nested state::active {
		width: 100%;
	}
}

states reference the overall component state

install

	npm install component-css

usage

var ccss = require('component-css');

ccss(/* Component Name */, /* source */, /* options */);

options

  • prefix (string)
  • spacing (string)
  • header (bool)