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

ngx-vector-components

v5.125.0

Published

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

Readme

NgxVectorComponents

This library was generated with Angular CLI version 13.1.0.

Summary

Library generated in order to share code between projects in the Vector ecosystem. Any component, styling, injectable, useful class or other types of code that would need to be copied between projects should be added here to be shared, avoiding duplication and improving their maintainability.

IMPORTANT

Any changes made to the library must be properly documented in the CHANGELOG.md file, using the proper semantic versioning as explained below:

Versions must be defined following the semantic versioning pattern, where the version number is divided into 3 segments, major, minor and patch versions, as in the example:

  • 2.5.3, where:
    • 3 = Patch (incremented when the new version is generated with FIXES only);
    • 5 = Minor (incremented when the new version receives NEW FEATURES);
    • 2 = Major (incremented when new version gets ANY BREAKING CHANGE).

Example of a breaking change: an input of some component has changed its typing or a change in behavior where it is necessary to make changes to the client code to continue working as expected).

  • Always keep the inputs, outputs and parameters of exported components/methods with proper TYPE.
  • 3 providers must be defined on the root level of the project: environment, appName, menuOptions. As shown below:

Generating version

After documenting the changes made, use the semantic versioning criteria to define the new version number and add this number to the library's CHANGELOG.md and package.json in the version field.

Build

After setting the version number in both files mentioned above: run npm run build in the root folder of the project, the command will generate the build of the library and place it in the dist folder of the root of the project.

Publishing

After successfully building the library, enter the dist folder and run npm publish.