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 🙏

© 2025 – Pkg Stats / Ryan Hefner

source-components

v1.3.2

Published

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 14.2.0.

Readme

SourceComponents

This library was generated with Angular CLI version 14.2.0.

Build

Run ng build source-components to build the project. The build artifacts will be stored in the dist/ directory.

Publishing

To publish a new version of the project you need to generate a personal access token on your azure account.

1. Generate access token

  • On your azure account access: User settings -> Personal access tokens;
  • Click on: New Token;
  • Fill in the form;
  • Name: the name of your access token;
  • Organization: klir;
  • Expiration: Set the expiration date that better fits your needs;
  • Scope: Full Access;
  • Click on create;
  • Now make sure to copy and SAVE the code because you won't be able to see this code again;
  • Encript this code to a BASE_64 format;

2. Build and publish

  • On the project access the file called .npmrc and add the following code:
; begin auth token
//pkgs.dev.azure.com/klir/Klir/_packaging/KlirAngularLibraries/npm/registry/:username=klir
//pkgs.dev.azure.com/klir/Klir/_packaging/KlirAngularLibraries/npm/registry/:_password=BASE_64_PASSWD
//pkgs.dev.azure.com/klir/Klir/_packaging/KlirAngularLibraries/npm/registry/:[email protected]
//pkgs.dev.azure.com/klir/Klir/_packaging/KlirAngularLibraries/npm/:username=klir
//pkgs.dev.azure.com/klir/Klir/_packaging/KlirAngularLibraries/npm/:_password=BASE_64_PASSWD
//pkgs.dev.azure.com/klir/Klir/_packaging/KlirAngularLibraries/npm/:[email protected]
; end auth token
  • Now put your BASE_64 access token on the _password field;
  • Remove the .npmrc file from git staging area: git update-index --assume-unchanged .npmrc;
  • Go to the file package.json and update the version;
  • Run: npm install && ng build source-components;
  • Copy and paste the file .npmrc to the dist/source-components folder;
  • Go to the dist folder cd dist/source-components and run npm publish.

Testing your modifications on the consuming project

  • After you finish your modifications run npm run sc:build to build the project;
  • Enter the dist folder cd dist/source-components;
  • Run npm link;

Now on the consuming project

  • Run npm link source-components;
  • Now you can test all of your modifications locally without the need to publish a new version;

Notes:

  • To unlink the project just run npm install;
  • If you want to test new modifications you'll need to run the build process again.

Running unit tests

Run npm run sc:test to execute the unit tests via Karma.