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

simulate-icore-service

v1.0.3

Published

To make it easy for you to get started with GitLab, here's a list of recommended next steps.

Readme

DOCUMENTATION FOR BUILDING, CONFIGURING AND DEPLOYING NPM PACKAGE TO GITLAB REGISTRY

Background

This package is for simulation purposes for usage in icore-service.

  • The packages directory in icore-service will be it's own library, the actual service will only required to install it like other npm library through npm install

  • This also will be combined with semantic version, where any changes made to the package, the versioning will be handled by semantic versioning convention: ->

  • This will be documentation of research on

    • Notes : what to be concerned of when using this workflow, and what adjustment required to be done to the existing project
    • Pros : what are the benefits of using this method
    • Cons : what are the down side of using this method
    • Credentials : list of credentials that needed from the org / BIB for this methods (email, password, token pattern, etc)
    • Workflow changes : what the impact of this implementation to new feature development, bug fixing, release, backward compatibility

NOTES

  • publishing private npm package require your payment detail to the npm package account, in this case if required for the organization, you must followup this detail to inquire the account to be used for deploying the npm package publicly