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 🙏

© 2026 – Pkg Stats / Ryan Hefner

my-container

v1.0.8

Published

Basic container to create a container

Readme

react-split-container

Folder Structure

  - build
  - config
  - node_modules
  - src
  - [reducers]
  - [constants]
  - [actions]
  - [actionCreators]
  .babelrc
  .eslintrc
  .gitignore
  .npmignore
  package.json
  README.md

Folders

  • build: Module build.
  • config: Module webpack config.
  • src: Container sources.

Files

  • .babelrc: here is defined the babel configuration about how transpile our code
  • .eslintrc / .eslintignore: here are defined the eslint configuration and ignored files
  • .npmignore / .gitignore: here are defined the files and foldes that we want to ignore for and npm

Development

  • Component must be created in src directory (entry must be index.js).
  • Keep watch for building changes.
  npm start

Working with containers

  • Containers will be rendered in routes and should have not any style configuration. Instead, containers use Layouts and Components. They can be installed via npm.
  import React from "react";
  import Layout from "some-project-layout";
  import Button from "some-project-component";

  export default class MyContainer extends React.Component {
    render() {
      const MyTitle = <h1>Title</h1>;
      const BoxButton1 = <Button>Button 1</Button>;
      const BoxButton2 = <Button>Button 2</Button>;
      const BoxButton3 = <Button>Button 3</Button>;
      return Layout ? (
        <Layout
          title={MyTitle}
          box1={BoxButton1}
          box2={BoxButton2}
          box3={BoxButton3}
        />
      ) : null;
    }
  }

Test your component

  • For testing your component you will need to link it to the project (Inside container folder)
  npm link

(Inside project folder)

  npm link container-name
  • Remember unlink component (Inside container folder)
  npm unlink

(Inside project folder)

  npm unlink container-name

Publish your component

(Inside container folder)

  npm publish

Working with redux

To make reducers and actions accesible they must be exported

import * as reducers from 'reducers'
import * as actions from 'actions'
import * as actionCreators from 'actionCreators'
import * as constants from 'constants'

// ...

export {
  reducers,
  actions,
  actionCreators,
  constants,
}