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

postcss-react-css-optimizer

v0.0.2

Published

Optimization of CSS by React components

Downloads

8

Readme

React CSS Optimizer (PostCSS plugin)

It's still in experimental stage

Remove unused CSS classes by analyzing React.Components JavaScript files. It's also support the use of the module classnames.

But what about CSS modules?

CSS modules is super cool! But I disagree about the way is solves the problem.

  1. CSS modules is more about preventing naming conflicts. While I prefer no uniqueness and more CSS classes shared between components (some references: cssguidelines, "The Top 5 Mistakes of Massive CSS")
  2. I don't like the idea of importing CSS in my JavaScript. And then find myself having more complexity in JavaScript and both CSS
  3. it's difficult to set the order of the rules when you import both CSS both in CSS files and JavaScript files

Usage

Installing from CLI:

 npm i --save-dev https://github.com/oriSomething/postcss-react-css-optimizer

Using it PostCSS:

const postcss = require("postcss");
const postcssReactCSSOptimizer = require("postcss-react-css-optimizer");

postcss([postcssReactCSSOptimizer({
  files: "react-component-file.js"
})]).process(/* ··· */);
// ···

Input:

component.js:

import ReactDOM from "react-dom";

export default function SomeComponent() {
  return <div class="will-exist" />;
}

component.css:

.will-exist { ··· }

.will-drop { ··· }

Output:

component.css:

.will-exist { ··· }

Roadmap

  • support pseudo and state selectors
  • support parent child relation CSS classes (example: .parent .child / .parent > .child)
  • show report of classes that have being dropped
  • support for more complex ways to extract CSS classes (example .selector-*. * is for everythig)
  • caching
  • non JSX support
  • maybe, changing the CSS tree and the JavaScript files, so many optimizations for CSS and CSS related in JavaScript files could be made
  • support of CSS classes with special characters (example .😁)