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

newcsslib

v1.0.2

Published

owr own css library

Readme

MCASS

====================

Hacktoberfest 2024

Welcome to MCASS, an open-source CSS library project for Hacktoberfest 2024. Your task is to contribute by adding new utility classes to the appropriate CSS files, running the build process, testing, and submitting a Pull Request.

Getting Started

Prerequisites

  • Node.js (latest version)
  • PostCSS (installed globally or locally)

Installation

  1. Fork the repo
  2. Clone the repository: git clone [repository link]
  3. Install dependencies: npm install

Contributing

Step 1: Choose a Category

Select the relevant CSS category (e.g., src/components, src/layouts, src/utilities) to add or modify classes.

Step 2: Add or Modify Classes

Add new classes or modify existing ones in the selected category.

Step 3: Run the build command

Build the CSS library: npx postcss src/index.css -o dist/csslib.css

Step 4: Test Your Changes

  1. run npm i
  2. Run npx postcss src/index.css -o dist/csslib.css to rebuild the CSS library.
  3. Open test.html and add your new class to test its functionality.

Step 5: Remove Test Class

Remove the test class from test.html.

Step 6: Clean Up Output CSS

Remove everything from dist/output.css.

Step 7: Commit and Push Changes

  1. Stage changes: git add .
  2. Commit changes: git commit -m "brief description of changes"
  3. Push changes: git push origin your-branch-name

Step 8: Create a Pull Request

Create a pull request to merge your changes into the main branch.

Guidelines

  • Follow Tailwind CSS's naming conventions and syntax.
  • Keep classes organized and sorted alphabetically.
  • Test changes thoroughly before committing.
  • Provide clear commit messages and PR descriptions.

File Structure

  • src/css/: Source CSS files, organized by category.
  • dist/: Compiled CSS library.
  • test.html: Test file for new classes.