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

demo-shared-entities

v1.32.12

Published

Add a .npmrc to your project, in the same directory as your package.json

Downloads

12

Readme

Project setup

Add a .npmrc to your project, in the same directory as your package.json

registry=https://pkgs.dev.azure.com/intouch-com/Intouch/_packaging/intouch-shared-supplier-demand/npm/registry/ 
                        
always-auth=true

Setup credentials

Step 1 : Add this code to .npmrc file

; begin auth token
//pkgs.dev.azure.com/intouch-com/Intouch/_packaging/intouch-shared-supplier-demand/npm/registry/:username=intouch-com
//pkgs.dev.azure.com/intouch-com/Intouch/_packaging/intouch-shared-supplier-demand/npm/registry/:_password=[BASE64_ENCODED_PERSONAL_ACCESS_TOKEN]
//pkgs.dev.azure.com/intouch-com/Intouch/_packaging/intouch-shared-supplier-demand/npm/registry/:email=npm requires email to be set but doesn't use the value
//pkgs.dev.azure.com/intouch-com/Intouch/_packaging/intouch-shared-supplier-demand/npm/:username=intouch-com
//pkgs.dev.azure.com/intouch-com/Intouch/_packaging/intouch-shared-supplier-demand/npm/:_password=[BASE64_ENCODED_PERSONAL_ACCESS_TOKEN]
//pkgs.dev.azure.com/intouch-com/Intouch/_packaging/intouch-shared-supplier-demand/npm/:email=npm requires email to be set but doesn't use the value
; end auth token

Step 2 : Generate a Personal Access Token with Packaging read & write scopes.

Step 3 : Base64 encode the personal access token from Step 2.

One safe and secure method of Base64 encoding a string is to:

  • From a command/shell prompt run:
node -e "require('readline') .createInterface({input:process.stdin,output:process.stdout,historySize:0}) .question('PAT> ',p => { b64=Buffer.from(p.trim()).toString('base64');console.log(b64);process.exit(); })"
  • Paste your personal access token value and press Enter/Return
  • Copy the Base64 encoded value

Step 4:

Replace both [BASE64_ENCODED_PERSONAL_ACCESS_TOKEN] values in your user .npmrc file with your personal access token from Step 3.

Installation

$ npm i @intouch/shared-entities-package