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

energize

v0.11.1

Published

React components for Materialize CSS

Downloads

50

Readme

Energize

React components (plus some styles) for Materialize CSS

Style Guide

JavaScript

  • Use ES6 features wherever possible, but avoid anything that requires es6-shim (Map, Set)
  • No jQuery or other large external dependencies
  • No direct DOM manipulation

Component State

UI components should strive to be as stateless as possible. However, there cases where this is not possible or desirable.

Any time we provide a stateful component, we should allow it to operate in "controlled" and "uncontrolled" mode, similar to how React handles form inputs.

We should always allow the user to provide one or more onChange (or similar) handlers as props. The component may perform any internal state bookkeeping whether or not change handlers are provided. If a change handler is provided, we should pass back any relevant events unchanged, along with any relevant data. If no change handlers are provided, we should preventDefault on any triggered events.

If a value prop (or whatever is appropriate for the component) is provided, then the component should defer to the given value instead of using its internal state. When a value prop is not provided, the component should track state internally.

Sass

  • Align property values on adjacent lines
  • Use scss-lint
  • Avoid changing Materialize styles wherever possible in order to maintain forward-compatibility

Class names

import cx from 'classnames';

const SpecialDiv = React.createClass({
  render() {
    // any classes we want to apply should come last so they override anything
    // set in this.props.className
    let classes = cx(this.props.className, 'top-nav');

    return (
      <div className={classes}>
        {this.props.children}
      </div>
    );
  }
});