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

hx-react-library

v0.1.0

Published

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

Readme

React

This project was bootstrapped with Create React App.

npm start

Runs the app in the development mode. Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits. You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode. See the section about running tests for more information.

npm test ${componentName} single component

You can test a single file by passing it's name.

Es:

npm test button

Test coverage

Test coverage goal at Helixa is setted to: 85% A report of coverage can be found by running:

npm run test -- --coverage

npm run build

Builds the app for production to the build folder. It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes. Your app is ready to be deployed!

See the section about deployment for more information.

Bit

Bit is a collaborative open source project.

At Helixa we use Bit for sharing reusable react component in every Helixa Front end project.

The hx-collection can be found here: https://bitsrc.io/helixa/hx-components

The Bit workflow

Add component to bit

When a new component need to be added to the bit collection you need to:

The collection is organized following the ATOMIC Design System, you can read more about that here (http://atomicdesign.bradfrost.com/)

  • add the component bit add src/components/atoms/Button -t 'src/components/atoms/Button/*.spec.js' --namespace atoms
  • tag the component bit tag atoms/button The tag method can be used with version parameters:
    • --patch 0.0.1
    • --minor 0.1.0
    • --major 1.0.0
    The bit tag method runs builds and tests automatically.
  • export components bit export helixa.hx-components

Linters and best practice

At Helixa we embrace the airbnb Javascript Styleguide: (https://github.com/airbnb/javascript) and we use the airbnb ES6 lint (https://www.npmjs.com/package/eslint-config-airbnb).

Css Style

The hx-component library and every project front end at Helixa uses Styled Components https://www.styled-components.com/

CircleCI

The reposistory is connected to to the continuous integration and delivery platform called CircleCI.

You can check the file on (.circleci/config.yml)

The pipeline is defined via workflows.

there two workflows defined: Test and Bit.

The Test job runs at every commit on every branch and is:

  • checking out the repo
  • npm install dependecies
  • running tests
  • updates coverage

If Tests are passed

The Bit job runs at every commit only on master branch and is:

  • checking out the repo
  • npm install dependecies
  • installs bit cli
  • authoring to Bit
  • checking out all latest versions of every component
  • tagging all components as patch
  • exporting to the colleciton
  • logs bit status