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

@sebgroup/chlorophyll

v3.3.5

Published

A CSS framework for SEB with accessibility at it's core.

Downloads

33,031

Readme

Install

It is not recommended to use Chlorophyll directly to style your own components - instead use what is available in the React or Angular libraries, or contribute what you are missing.

Use

The Green design system has an unrelenting focus on sensible defaults and ease of use. All you have to do to start using it is import the css, mark the area in which you intend to start using Green (use the html tag if the whole application uses it), and add the class use-green (we recommend that you scope the CSS so that it only affects elements yo intend to style).

<body class="use-green">
  <h1>Hello!</h1>
  <p>Everything you see here will be correctly styled :smile:</p>
</body>

All your basic styling will now be correct. Additional classes will only be needed when you want to deviate from the defaults. So this:

<div class="use-green">
  <form>
    <div class="form-group">
      <label for="formInput1">Input</label>
      <span class="form-info" id="formInfo1">Some info or help</span>
      <input id="formInput1" type="text" aria-describedby="formInfo1" />
    </div>
    <button type="submit">Send</button>
  </form>
</div>

...will look like this:

Additional styling

Styling is made by expressing intent – not design. A button is not green, it is intended to express a successful operation. So:

<!-- This -->
<button class="success">Yay!</button>

<!-- Not this -->
<button class="light-green">Derp!</button>

To find all components, possible modifiers and information on when to use them, visit:

  • Storybook for Angular
  • Storybook for React
  • Storybook for html/css (for when you definitely don't need a framework)

Missing components and/or help

If you cannot find the component you're looking for and/or want help switching to Green, see information on Green pilots

If you are up and running with Green and want to contribute a new component, see Contributions

Contribute

This is part of a monorepo. If you want to contribute, see Green