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

stylie-mcstyleface

v1.2.1

Published

Like free-style, but with tagged template strings and SASS

Downloads

9

Readme

Stylie McStyleface

Tagged template strings for SASS. Uses node-sass so not useful for client-side code.

The intended use-case is for rendering static sites with JS and React, but keeping the styles in the same files as the code. I was previously using free-style but struggled with its lexicographic approach to rule ordering (bad news for @media queries). It also fails silently way too often and has some bugginess around deeply-nested things. All this led me to a comparatively simple approach.

import style from 'stylie-mcstyleface';

// include global rules
style.rules `
  body {
    font-size: 12pt;
  }

  @media (min-width: 90000px) {
    font-size: 500pt;
  }
`;

// or define anonymous classes
const className = style.register `
  color: #777;
  &:hover {
    color: #222;
  }
`;

className // => 'mc1igb8ty'

// and use them in JSX or wherever
const elem = <div className={className}>some content</div>;

Accumulated styles can be retrieved with the .getCSS method.

style.getCSS();
// body {
//   font-size: 12pt; }
//
// @media (min-width: 90000px) {
//   font-size: 500pt; }
// .mc1igb8ty {
//   color: #777; }
//   .mc1igb8ty:hover {
//     color: #222; }