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

boilerplate-react-component

v0.0.8

Published

A React component boilerplate

Downloads

11

Readme

Build Status

component-boilerplate

You can view a demo here;

Quick Start

  • npm i
  • npm run i:demo
  • npm start

Publishing

In order to publish and deploy your new package via TravisCI, you need to go through the following three steps.

  1. Modify the .travis.yml with your own npm details. The simplest way to do this is by following this guide or running travis setup npm.

  2. To deploy the demo to a gh-pages branch you need to make a Github token with repo access on process.env.GITHUB_TOKEN or run travis encrypt -r GITHUB_TOKEN=[the token here] to add it to your travis.yml. Be warned if you have collaborators, this gives access to all repositories. Note: A project specific SSH key would prove safer. Look into adding this.

Finally once the above has been set up, you can run npm version <newversion> as per the npm docs. This will create a tagged commit that is pushed to the repository and will start the TraviCI process deployment process.

TODO

  • Install demo dependencies as post install
  • Better build logging
  • Remove dist from importing css files.
  • define plugin for process.env variables.
  • Document