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

b2b-core-libs-nodejs

v1.0.0

Published

core libraries for framework

Readme

b2b-core-libs-nodejs

This project is a monorepo using npm workspaces (lerna free). Contains some core libraries used in our nodejs API projects (including the new version of the framework)

Publishing a package

The packages are published at ingka-b2b-components-prod project.

Steps

  1. authenticate
  2. go to the package folder
  3. set version
  4. publish

Authenticate to publish

Add the following lines you your home's .npmrc (this will be necessary to consum the modules as well)

@box:registry=https://europe-npm.pkg.dev/ingka-b2b-components-prod/box/
//europe-npm.pkg.dev/ingka-b2b-components-prod/box/:_authToken=""

Now you need an auth token to publish them so let's change your gcp project and get this token:

gcloud auth login
gcloud config set project ingka-b2b-components-prod
npx google-artifactregistry-auth

Set version

Change the version of the package you want to publish with npm version XXXX

where XXXX:

  • major
  • minor
  • patch
  • premajor
  • preminor
  • prepatch

If you want to publish a beta, change the version manually in your package.json: add beta.x (where x is a number).

For example, if your package is in 1.0.0 version, you could publish the 1.0.1-beta.1. If you need to make some changes after this publication, change the version to 1.0.1-beta.2, then 1.0.1-beta.3, ... and when your module is ready, just left 1.0.1 as version.

Publish

Be sure you are in the package folder and just type: npm publish

If yo want to publish a beta version, type npm publish --tag beta instead. Remember to first establish the version in the package.json.

zzz