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 🙏

© 2024 – Pkg Stats / Ryan Hefner

htz-commons-lib

v1.6.31

Published

A suite of different libraries that allow you to ensure values of certain types

Downloads

32

Readme

Build Status

htz-commons-lib

Install

$ npm install htz-commons-lib

Development workflow

  • Unit test your code

  • Do your changes

  • To test all functions, run npm run test

  • To unit test only certain functions, rename your spec file to {filename}.xspec.ts

  • Then run npm run test:xpec. This will test files with

  • When you are done with your changes, commit your work and then npm version patch

    • A few actions will take place:
    • The hook preversion is executed and runs the lint
    • The code is automatically formatted by prettier
    • Git adds every single file changed in src
    • The hook postversion is executed and will run: git push && git push --tags
    • The code is committed and sent to the repo

    • ... Check https://docs.npmjs.com/misc/scripts for more information on npm scripts execution order