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

pcm-shared-components

v2.1.286

Published

The Library is published to NPM on the github build.

Readme

Shared Components between client and admin portal

The Library is published to NPM on the github build.

Deploying

  • When the code is checked into Github it will publish it automatically if the package.json version is bumped.

Manual Deploy

Manually deploying is faster then committing the code as it doesn't need to create a ful build.

# Must build the Storybook dist folder before manually publishing
> npm run build

# Edit the package.json file and up the version.
> npm version patch --force

# Login if not already logged in
> npm login

# Publish your new library
> npm publish

# Update the library in other projects by running the following
> npm install pcm-shared-components@latest

# Or run the following to do it all in one go!
sh ./publish.sh

# Or you can also run the following npm to do it all in one go!
> npm run bump

# Update the remote Library

```npm run bump``` - This will bump the version of the library and push it to the remote repository.


------------------------------------------------------------------------------------------------------------
## Environment (.env)

Copy `.env-template` and rename it to `.env`.

Create a granular access token at [https://www.npmjs.com/settings/tokens](https://www.npmjs.com/settings/tokens) with publish permission.

Place your token inside the `.env` file:

NPM_TOKEN=your_npm_token_here

The token will be used automatically during release and publishing.


------------------------------------------------------------------------------------------------------------

# ##########################################################################
# Upgraded Node Modules from 14 to 20 (Nov 15, 2025)
# ##########################################################################

Steps needed to upgrade node modules to version 20 on your local machine:
- delete the node_modules folder
- delete package-lock.json
- previous version was: v14.18.0
- nvm install 20.19.5
- nvm alias default 20.19.5
- nvm use 20.19.5
- echo "20.19.5" > .nvmrc
- nvm use
- npm install
- npm start

------------------------------------------------------------------------------------------------------------


# Future Migration TODO:

- Storybook Upgrade:
    - I tried to upgrade to the latest version of Storybook v10 but it needs react 18 which I'm not ready to do yet.
    - So for now i'm sticking with version 6.
- As for Vite:
    - because i'm on storyboard 6 I would need VITE v4 which is only supported on node 14-16 which I'm on v20. 
    - So for now I'm sticking with webpack 5.
- [email protected] target 18.x when possible
- refresh ESLint to version 8.x when possible
- Drop babel-eslint in favor of @babel/eslint-parser when possible