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

which-tachyons-module

v0.3.0

Published

Small module for finding the specific Tachyon modules you've used

Downloads

4

Readme

which-tachyons-module Build Status js-standard-style

Small module for finding the specific Tachyon modules you've used. When I build new things with Tachyons, I usually just use the CDN or include the base package. This works, but when I later want to cut down the CSS bundle size because I don't realistically use all of Tachyons it's tough figuring out exactly which modules I have used. This little command line tool helps with that.

Installation

npm install -g which-tachyons-module

Usage

which-tachyons-module takes a .html file as input and outputs the various Tachyons modules used in that .html file based on its classes.

$ wtm index.html

# Outputs e.g.
# tachyons-borders tachyons-border-widths tachyons-heights tachyons-spacing

License

MIT

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

Crafted with <3 by which-tachyons-module (@br11x).


This package was initially generated with yeoman and the p generator.