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

dealer-hub

v1.0.22

Published

It contains all shareable components of dealer portal and dealer apps

Readme

Dealer hub

This project contains components and services used for dealers.

Contents

1 Project structure

  • Library:
    • lib folder for the classes
    • public_api.ts entry point for all public APIs of the package
    • package.json npm options
    • rollup.config.js Rollup configuration for building the umd bundles
    • rollup.es.config.js Rollup configuration for building the es2015 bundles
    • tsconfig-build.json ngc compiler options for AoT compilation
    • build.js building process using ShellJS
  • Testing:
    • tests folder for unit & integration tests
    • karma.conf.js Karma configuration that uses webpack to build the tests
    • spec.bundle.js defines the files used by webpack
  • Extra:
    • tslint.json Angular TSLint Preset (TypeScript linter rules with Codelyzer)

2 Installation

Install the npm packages by running the following command:

npm run build

4 Building

The following command:

npm run build
  • starts TSLint with Codelyzer using Angular TSLint Preset
  • starts AoT compilation using ngc compiler
  • creates dist folder with all the files of distribution, following Angular Package Format (APF) v5.0:
└── dist
    ├── bundles
    |   ├── dealer-hub.umd.js
    |   ├── dealer-hub.umd.js.map
    |   ├── dealer-hub.umd.min.js
    |   └── dealer-hub.umd.min.js.map
    ├── esm5
    |   ├── dealer-hub.js
    |   └── dealer-hub.js.map
    ├── esm2015
    |   ├── dealer-hub.js
    |   └── dealer-hub.js.map
    ├── src
    |   └── **/*.d.ts
    ├── dealer-hub.d.ts
    ├── dealer-hub.metadata.json
    ├── LICENSE
    ├── package.json
    ├── public_api.d.ts
    └── README

To test locally the npm package before publishing:

npm run pack:lib

Then you can install it in an app to test it:

npm install [path]dealer-hub-[version].tgz

4 Testing

The following command runs unit & integration tests that are in the tests folder (you can change the folder in spec.bundle.js file):

npm test 

or in watch mode:

npm test:watch

It also reports coverage using Istanbul.

5 Releasing

The following command will pack the dist folder and push it to the release branch:

npm run publish:lib

Then a github release can be formed against the release branch based on the build version

6 Documentation

To generate the documentation, this starter uses compodoc:

npm run compodoc
npm run compodoc:serve 

7 Demo

  1. Go to Demo folder and import respective component in app.component.js
  2. Add selectors in html file if its component.
  3. For service. Import service and add it in providers and call those services.
  4. Run npm start - It will build package and link it with demo project and then start demo project.