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

ship-my-component-npm

v0.1.0

Published

adds webpack and some folder conventions to let you publish components to npm publically.

Downloads

7

Readme

ship-my-component-npm

adds webpack and some folder conventions to let you publish components to npm publically.

Great for open sourcing a single component folder of your react application, such as releasing a login screen for people to utilize and modify.

Verified working on Ubuntu-Linux ✅ Macintosh Mojave ✅

npx ship-my-component-npm

## cleanup
npx ship-my-component-npm cleanup

Linux Users

# ensure expect is installed
sudo apt-get install expect;

# expect is a unix program that comes by default on a mac. It allows your program to interact with another applications prompt. This project uses expect to interact with npm init. Decreasing the amount of prompts from 8 prompts to 3 prompts.

Try out a previously published react component:

run this command in the terminal

npm install react-publish-ship

include the nodemodule in your react project

import ReactPublishShip from 'react-publish-ship';
...
render(){
  <div>
    <ReactPublishShip />
  </div>
}
...

This project was made possible thanks to the following blog post: https://medium.com/@BrodaNoel/how-to-create-a-react-component-and-publish-it-in-npm-668ad7d363ce

In the article a src directory is used. This project has changed the webpack config so as to use the current directory not a src directory.

Why does this project use a build directory but not a src directory.

React follows a convention where the index.js file is responsible for exporting contents of a folder.

Per request, additional modifications could be added to make these scoped packages so that they stay within a company.

Let me know if you find this useful, on twitter m_dimmitt

Open an issue for a feature request or to report an issue.

Thanks!!

Current Contributors: Vladamir Pliuta Michael Dimmitt

Known projects published using ship my component: (feel free to submit a pr if you published a react component!)

react-publish-ship source hello-world-npm-component source

Below is a project with a ton of components, using the script for this project I could easily share a front end component with the outside world. Screen Shot 2019-06-03 at 1 48 49 PM