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

aetna

v1.0.2

Published

Front-end style guide and pattern library for Pressbooks.

Downloads

60

Readme

Aetna

Front-end SCSS component library for Pressbooks.

Usage

  1. Install via npm: npm install aetna --save.
  2. Import into your project's Sass files:
@import "~aetna/assets/styles/aetna.scss";

Development and testing

Use Conventional Commits. This helps generate a CHANGELOG automatically.

Sass goes in assets/styles.

Components are documented using Fractal. Fractal source goes in src.

Run Stylelint on your Sass: npm run lint

Run a test build to ensure that your Sass compiles without issue: npm run build

Releasing

  1. Run npm run production to generate an updated stylesheet for the component library which is published at https://aetna.pressbooks.org.
  2. Commit the changes using the chore scope in your commit message: git commit -am "chore(build): build stylesheet
  3. Push this change to GitHub.
  4. Inspect the automatically generated release pull request.
  5. If it looks good, you can merge it which will tag a new version and create a new GitHub release.
  6. Pull the latest changes into your local environment, then run npm publish.