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

bea-ui

v0.3.0

Published

React component library

Downloads

22

Readme

Bea UI

React Web Components

Getting started

Clone the repo and install Node dependencies

git clone https://github.com/craigharvi3/bea-ui.git
yarn install

Development

Components

Getting started

  • Run yarn styleguide, this command will start a server at http://0.0.0.0:6060 and watch for changes in the code.
  • React components live in the components folder. Each component should be built in its own folder using Atomic design.

Testing components

We are using Mocha, Enzyme and Sinon to test components.

  • Create component-name.test.js in the component folder.
  • Components generally have a should render and should not render describe block as a minimum.
  • Run yarn test

Production

  • Run yarn add bea-ui to include the library from NPM.
  • Import the component in your page: import { Component } from 'bea-ui';

Publish styleguide

To see changes in Bea UI on <insert styleguide link here>, styleguide needs to be published.

  • Run yarn styleguide:publish from master

How is it published:

gh-pages is a branch used by GitHub to create public version of the styleguide.

yarn styleguide:publish is running git subtree push --prefix styleguide origin gh-pages, to copy the contents of /styleguide directory into gh-pages branch.

Release to NPM

  1. Bump version in package.json as part of the pull request.

  2. Update /dist folder with the latest version:

yarn build
  1. Publish the styleguide (yarn styleguide:publish) from master.

  2. Log in to NPM:

npm login
  1. Once the pull request is merged, check out the master branch, and publish from master:
npm publish
  1. Create tag corresponding to the package version.
git tag -a v1.4.2 -m "Release 1.4.2"
git push --tags
  1. Create the release on GitHub. Describe release on GitHub using release template from any.