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

bodyspec-shared-components

v0.1.0

Published

BodySpec Shared UI components

Readme

#BodySpec/Shared Components

The repo contains shared UI components, that can be used in the intakes and the main web application. The components are created using Bootstrap v5.


##Development

For the components development Storybook is used here.

To run Storybook server, run yarn storybook


##Approach

To create or debug a component - create a story for your component using such naming template: YourComponent.stories.tsx. See more details

Each component should have unit tests for that, based on the snapshot testing.


##Code Style and Testing

There are some code rules we should follow. There are applied eslint, ts and stylelint rules. To check your code use command yarn code_style. To fix code issues - yarn code_style:fix.

To run unit-tests use yarn test command. If you want to update snapshots - use yarn testu.


##Publishing

Notice, before each publish it's required to run all code checks, tests and build the lib. It's run automatically. Use yarn lib:build command.

To publish the library use command yarn lib:release.