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

@smartviser/core-lib

v0.7.4

Published

The main goal of this project is to share common code/components/constants between VWS ui applications.

Downloads

666

Readme

VWS ui applications

The main goal of this project is to share common code/components/constants between VWS ui applications.

How does it work ?

Exports

Every services or component that you want to use in another project should be exported in public_api.ts

What's inside ?

Shared modules, ex: navbar

The shared modules are groups of components, which will be reused in several VWS applications.

Regarding the code architecture of the first module, navbar is composed of:

  • a main component, which acts like a container
    • its template contains the child components (see navbar.component.html)
    • the component's class contains the business logic of all the module (see navbar.component.ts)
  • child components
    • these are just presentational components, the data is passed down through these components

api

Services created to communicate with our REST API back-end

constant

Define here the const declarations that we should not be able to re-assign (ex: VWS user's roles)

model

Define contracts for the "shape" of your values (ex: a User interface with firstname, lastname, etc.)

util

Utility services, these files contain reusable functions and services (ex: DateService)

assets

Some images and .less files

How to use this lib in another project ?

Add <@smartviser/core-lib : version> in your package.json.

You can use and display a shared module in your project by importing its main component.
To import component : <import { NavbarModule } from '@smartviser/core-lib';> The prefix used here is "vws".
For example:

<vws-navbar [parentService]="$service"></vws-navbar>