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

@juvare-oss/test-public-package

v0.0.1

Published

This is a common library.

Readme

${common-library}

This is a template project for developing common library.

After creating a project using this template don't forget to update this README.md, package.json, CONTRIBUTING.md and CHANGELOG.md files according to your project

Installing

$ npm i @juvare/${common-library}

Note for Windows users:

  1. Build scripts, version increment scripts won't work on Windows, use Git Bash to run those.
  2. Linting is checking line endings, .gitattributes file should take care of that. If not, you can also try git config --global core.autocrlf false (probably that will need cloning from scratch).

Versioning

This project adheres to Semantic Versioning.
We publish NPM modules to our GitLab server: https://gitlab.juvare.com/common/npm-registry/-/packages

Development Workflow

Implementing Features or Fixing Defects

  1. Create a feature/* or bugfix/* branch from main.
  2. Write the code.
  3. Determine which version number to increment: MAJOR, MINOR or PATCH.
  4. Increment the version number by running a command (see "Incrementing Version Numbers").
  5. Create a pull request from your branch to main branch.
  6. Review and merge the pull request.
  7. CI/CD automatically builds and publishes the library.

Incrementing Version Numbers

Always use these commands to increment version numbers.

| Version | Command to Run | | ------- | --------------------------- | | MAJOR | npx library version major | | MINOR | npx library version minor | | PATCH | npx library version patch |