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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@stempelv/ng-builders

v1.0.28

Published

Custom builder for Chrome extension

Readme

@stempelv/ng-builders: Angular Builder for Chrome Extensions

npm version

This repository contains a custom Angular CLI builder (@stempelv/ng-builders) for building Chrome Extensions.

The builder streamlines the development of Chrome extensions by:

  1. Executing the standard Angular application build (@angular-devkit/build-angular:browser) to compile the main application, which can be used as a popup or options page.
  2. Using esbuild to compile and bundle browser-specific scripts, such as background.ts and content.ts, into the final output directory.

Installation

To install the builder, run the following command in your Angular project:

npm install @stempelv/ng-builders --save-dev

or

pnpm add @stempelv/ng-builders --save-dev

Usage

To use the builder, you need to configure it in your angular.json file. Replace the default build builder with the custom extension builder.

Here is an example configuration:

// In angular.json
"architect": {
  "build": {
    "builder": "@stempelv/ng-builders:extension",
    "options": {
      "backgroundScript": "src/background.ts",
      "contentScript": "src/content.ts",
      "manifest": "src/manifest.json",
      "outputPath": {
        "base": "dist/my-extension"
      },
      "tsConfig": "tsconfig.app.json",
      "assets": [
        "src/favicon.ico",
        "src/assets"
      ],
      "index": "src/index.html",
      "main": "src/main.ts",
      "polyfills": "src/polyfills.ts"
    },
    "configurations": {
      "production": {
        "fileReplacements": [
          {
            "replace": "src/environments/environment.ts",
            "with": "src/environments/environment.prod.ts"
          }
        ],
        "optimization": true,
        "outputHashing": "all",
        "sourceMap": false,
        "extractCss": true,
        "namedChunks": false,
        "extractLicenses": true,
        "vendorChunk": false,
        "buildOptimizer": true,
        "budgets": [
          {
            "type": "initial",
            "maximumWarning": "2mb",
            "maximumError": "5mb"
          }
        ]
      }
    }
  },
  // ... other architect targets
}

Then, you can build your extension by running:

ng build

Builder Options

The following options are available for the extension builder:

| Option | Type | Description | | ------------------ | --------- | -------------------------------------------------------------------------------------------------------- | | watch | boolean | Rebuild on file changes. Defaults to false. | | backgroundScript | string | Required. Path to the background script (e.g., src/background.ts). | | contentScript | string | Required. Path to the content script (e.g., src/content.ts). | | manifest | string | Required. Path to the manifest file (e.g., src/manifest.json). | | outputPath | object | Required. An object defining the output paths. | | outputPath.base | string | Required. The base output path relative to the workspace root (e.g., dist/my-extension). | | outputPath.browser| string | The output directory name for the browser build within the base path. Defaults to browser. |

Any other options valid for the standard @angular/build:application builder (like tsConfig, assets, styles, etc.) can also be used.