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

@adzn1/jobber-shared

v0.0.6

Published

Shared interfaces and utilities for Jobber

Downloads

1

Readme

Shared Library The shared library contains codes that are used acrossed the microservices. The idea behind this was to prevent code duplication. The library is published as an npm package to github package registry. You need to publish this shared library to github package registry to be able to use it. Steps required to publish your package Clone or download this repo Open the project in a terminal and remove .git folder from the package On Unix, run rm -rf .git On Windows, you can use git bash or show hiddens files Execute git init command inside the project. Create a personal access token on github. Export the token locally with key NPM_TOKEN. Keep the personal access token because it will be needed. In your .npmrc file, add @:registry=https://npm.pkg.github.com/ //npm.pkg.github.com/:_authToken=${NPM_TOKEN} Replace with your github username. In your Package.json file, add the value to the following fields name: @/ author: url: git+.git You can update the dependencies and devDependencies. In the .github/workflows folder, replace inside the publish.yml with your own github username. You can change the node-version to something higher. Create your own github project for the package. Push the code to github. Once you push, a github actions build will be triggered. If no error, your package will be published. Import Whenever you make any change to the shared library folder, make sure to increment the version number inside Package.json file.