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

@pushpalatha_h/test-package

v0.0.2

Published

This project demonstrates how to build a monorepo of dependent components that are installed as a single package. It builds a library of components similar to Angular Material.

Readme

Dmv

This project demonstrates how to build a monorepo of dependent components that are installed as a single package. It builds a library of components similar to Angular Material.

Most of the nx commands work as expected with the exception of those that are dependent the dep-graph. Commands that use affected don't work either.

Building The Library

To build the component library for distribution run

npm run build-libs

This triggers a sequence of build scripts in the package.json to build the components in their order of dependencies.

Consuming The Library

This library builds the set of components that are installed using a form like

npm install @namespace/library

This installs the collection of components in the project.

Angular Material supports 2 styles of importing into applications:

import { CoreModule } from '@dmv/demo'`
import { CoreModule } from '@dmv/demo/core'

This repo supports the latter style only.

Project Structure and Building

In nx parlance, a library is a unit of dependency and build which can include one or more angular components.

In this instance, we treat and think of the nx library as a component.

Building the component for distribution is a matter of configuring the ng-packagr control files.

Configure Component ng-package.json

Define the destination based on the desired distribution package structure:

  "dest": "../../dist/@dmv/demo/button",

The umdId provides the id for the module. The map of umdModuleIds keeps the complier from guessing about the dependencies:

    "umdId": "dmv.button",
    "umdModuleIds": {
      "@dmv/demo/core": "dmv.core",
      "@dmv/demo/link": "dmv.link"
    }

Configure Component package.json

The main thing to configure here is the component name including the npmjs namespace:

  "name": "@dmv/demo/button",

Configure Component tsconfig.lib.json

When a component is built it reads the source for the component from the src/libs path. The dependencies for the component must be resolved from the previously built components. To enable this we need to add the path to the compiler options:

  "compilerOptions": {
    ...
    "paths": {
      "@dmv/*": ["dist/@dmv/*"]
    }
  },

Configure Repo tsconfig.json

In order for Visual Studio Code to resolve the dependencies we need to configure the components in the project level tsconfig.json

  "compilerOptions": {
    ...
    "paths": {
      "@dmv/demo/core": ["libs/core/src/index.ts"],
      "@dmv/demo/button": ["libs/button/src/index.ts"],
      "@dmv/demo/link": ["libs/link/src/index.ts"]
    }
  },