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

integratedcss

v0.0.6-alpha

Published

Integrate CSS into your React.js component

Downloads

4

Readme

IntegratedCSS

After integrating HTML into JavaScript by React.js, a logical next step is to do the same for CSS.

Build with help of the awesome recast library.

Example

var Button = React.createClass({

  css: function() {
    var vars = require('./vars'); // vars.js would export a black variable
    return {
      state1: {
        backgroundColor: vars.black
      },
      state2: {
        backgroundColor: 'white'
      }
    }
  },

  getInitialState: function() {
    return {
      hover: false
    };
  },

  render: function() {
    var css = this.state.hover ? this.css().state2 : this.css().state1;
    return <div className={css}>Example</div>;
  },

  onMouseOver: function() {
    this.setState({hover: true});
  }

});

Turns into:

css:
---
.a {
  background-color: 'black';
}
.b  {
  background-color: 'white';
}

JavaScript
---
var Button = React.createClass({

  getInitialState: function() {
    return {
      hover: false
    };
  },

  render: function() {
    var css = this.state.hover ? " a" : " b";
    return <div className={css}>Example</div>;
  },

  onMouseOver: function() {
    this.setState({hover: true});
  }

});

Why?

CSS is problematic to maintain and components give all the borders you actually need.

What does it actually do?

  • It takes out the css function and transform it into plain CSS
  • The css function is executed on its own, it has no reference to 'this'
  • connect the (something.)css.something blocks to CSS
  • create CSS with annoyingly small CSS className selectors (3 characters max - up to 140608 classes)
  • CSS is coupled to the component and can be passed to another component via props (aProp={this.css.something})
  • isn't smart about actual references to the CSS object

Usage

node TransformerCLI.js --input=example/**/*.js --output=build/ --css=build/styling/lala.css

LICENSE

MIT