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

react-statics

v1.0.2

Published

Decorate React components with static properties

Downloads

318

Readme

react-statics

Decorate React components with static properties

Table of contents

Summary

When working with stateless functional components, or overriding default values on decorated components, applying statics can feel a bit boilerplate-y. This decorator centralizes the static property assignment, and allows for easy decorated composition.

Usage

Standard

import React from "react";
import statics from "react-statics";

const App = ({ foo }, { bar }) => (
  <div>
    {foo}: {bar}
  </div>
);

export default statics({
  contextTypes: {
    bar: PropTypes.node.isRequired
  },
  displayName: "MySpecialApp",
  propTypes: {
    foo: PropTypes.string.isRequired
  }
})(App);

Composed

import React from "react";
import { translate } from "react-i18next";
import { connect } from "react-redux";
import statics from "react-statics";
import { compose } from "redux";

const App = ({ foo }, { bar }) => (
  <div>
    {foo}: {bar}
  </div>
);

export default compose(
  statics({
    contextTypes: {
      bar: PropTypes.node.isRequired
    },
    displayName: "MySpecialApp",
    propTypes: {
      foo: PropTypes.string.isRequired
    }
  }),
  translate(["namespace"]),
  connect(({ reducer }) => reducer)
)(App);

NOTE: To ensure the values passed override any assigned by other composed decorators, place statics last to execute in the composition chain.

Development

Standard stuff, clone the repo and npm install dependencies. The npm scripts available:

  • build => run rollup to build development dist files
  • clean => run clean:dist, clean:es, and clean:lib
  • clean:dist => remove all existing files in the dist folder
  • clean:es => remove all existing files in the es folder
  • clean:lib => remove all existing files in the lib folder
  • dev => run webpack dev server to run example app / playground
  • dist => runs clean:dist and build
  • lint => run ESLint against all files in the src folder
  • lint:fix => run ESLint against all files in the src folder, fixing anything it can automatically
  • prepublish => runs prepublish:compile when publishing
  • prepublish:compile => run lint, test:coverage, transpile:lib, transpile:es, and dist
  • test => run AVA test functions with NODE_ENV=test
  • test:coverage => run test but with nyc for coverage checker
  • test:watch => run test, but with persistent watcher
  • transpile:lib => run babel against all files in src to create files in lib
  • transpile:es => run babel against all files in src to create files in es, preserving ES2015 modules (for pkg.module)