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 🙏

© 2025 – Pkg Stats / Ryan Hefner

react-ui-modules

v0.0.1-beta-12

Published

A simple set of base components that can be extended to build better UI with less work.

Readme

h1. Overview

A common set of UI elements that can be reused in any React project.

NOTE: This module is still in early stages of DEVELOPMENT, Its API's are not stable yet, and are subject to change.

h1. Development

When developing you will need to have another react app that you want to import this module into.

We’ll need an app to experiment with our components locally. You can use an existing react project, or use something simple like https://github.com/facebookincubator/create-react-app.

h2. Linking our Library

NOTE: You’ll probably want to keep your component library open in one terminal pane and your test app in another.

First you need to create a symlink of the library locally (If you’d like to learn more about npm link, check out https://docs.npmjs.com/cli/link.) from the root of the component library, run yarn link link. You’ll notice this will also run the prepublish script in the console, this will conduct the initial build of the module.

You can now run the start:development command, this will keep an eye on any changes and update the build and symlink whenever anything changes. This allows us to develop in the local module, and see the results in our linked project.

Now we’ll tell our other app that we want to use that symlinked library. From the root of your included app run yarn link react-ui-modules.

You can now include the component you wish to work on in your other app include {Button, Form} from 'react-ui-modules'. Changes made to the module will be made available to the linked project via the symlink.

h2. GIT

This module makes use of the Gitflow workflow for managing its git versioning and bug fixes. Learn more at https://nvie.com/posts/a-successful-git-branching-model/ or https://danielkummer.github.io/git-flow-cheatsheet/

h2. Dev Plugins This tool is build for React projects. This allows us to make use of some of the very useful react development tools.

I recommend installing:

  • React Developer Tools - https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi?hl=en
  • Redux DevTools - https://chrome.google.com/webstore/detail/redux-devtools/lmhkpmbekcpmknklioeibfkpmmfibljd?hl=en

h1. Publish

To publish a new version of the module to NPM push all changes to the GIT repo master branch, then use the yarn publish command to push the changes. This will run the prepublish script to build the module before pushing up the changes. Make sure to increment the version making use of the NPM semantic versioning or users may not be able to update to the latest version. (Learn more about about NPM semantic versioning at https://docs.npmjs.com/getting-started/semantic-versioning)