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

bright-components

v10.2.9

Published

[See latest components here.](https://brighthr.github.io/BrightComponents/)

Downloads

2,892

Readme

React Components

See latest components here.

Developing with WebApp

Npm allows you to point at any github branch, develop your component first, push to your branch, and point WebApp bright-components to that branch.

In order to do that, update package.json with the commit hash you require and do an npm install.

"bright-components": "github:brighthr/brightcomponents#eff943143d40f95cf0cc2695ca888bce8f95dc04"

It is also possible to use the branch name, but if you push further commits you'll need to use npm update: "bright-components": "github:brighthr/brightcomponents#test-version"

Once demoed and tested, merge your bright-components PR to master.

Update the reference in WebApp to point to published version.

Component Library

We use Styleguidist to provide living documentation for the components.

Run npm run styleguide and then hit http://localhost:6060. This will update as you add to your component.

Windows devs

You'll probably want to run the following commands within the repo to ensure consistent line endings, since whilst Git will convert them for you, the linter expects LF, not CLRF:

$ git config core.eol lf
$ git config core.autocrlf input
$ git checkout-index --force --all

Generating icons

Create a new directory icons in root, if one does not already exist on your local machine. Add the icon.svg to this folder. Run the genIcons.js script with the following command npm run genIcons. Delete icon.svg from the icons directory.

Versioning

We use semactic-release package to automate versioning and deployment to NPM. Commit messages should adhere to conventions here.

Here is an example of the release type that will be done based on a commit messages:

Patch Release:

fix(pencil): stop graphite breaking when too much pressure applied

Feature Release:

feat(pencil): add graphiteWidth option

Breaking Release:

feat(Modal): add new required prop to ModalBREAKING CHANGE: All modals need GA prop now.

  • When you squash and merge a PR onto master, make sure you put a "BREAKING CHANGE:" line in the commit message section.

example