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

@da-mkay/ng-builder-typescript

v20.0.1

Published

A set of builders and schematics for the Angular CLI to build Node.js apps using the typescript compiler tsc (no webpack or any other bundler used).

Downloads

44

Readme

@da-mkay/ng-builder-typescript

A builder for the Angular CLI to build Node.js apps using the typescript compiler tsc (no webpack or any other bundler used).

Versions

This version of @da-mkay/ng-builder-typescript requires Angular 20. Use the tag ng20 when installing this version, like so:
ng add @da-mkay/ng-builder-typescript@ng20

For other Angular versions take a look at the table below or at the Versions page. | Angular Version | Tag for @da-mkay/ng-builder-typescript | | --------------- | ---------------------------------------| | Angular 20 | ng20 | | Angular 19 | ng19 | | Angular 18 | ng18 | | Angular 17 | ng17 | | Angular 16 | ng16 | | Angular 15 | ng15 | | Angular 14 | ng14 | | Angular 13 | ng13 | | Angular 12 | ng12 | | Angular 11 | ng11 | | Angular 10 | ng10 | | Angular 9 | ng9 | | Angular 8 | ng8 |

Table of Contents

Start project from scratch

First create a new empty workspace:

$ ng new workspace --create-application=false
$ cd workspace

Then install the builder:

$ ng add @da-mkay/ng-builder-typescript@ng20

(Using the tag ng20, the Angular 20 compatible version will be installed)

Finally create a new Node.js/typescript project:

$ ng g @da-mkay/ng-builder-typescript:app

You will be prompted for the project name. In the following examples PROJECT is used for the project name and must be replaced in your case accordingly.

To compile the project run:

$ ng build PROJECT

By default, the compiled code is written to the dist/ folder. You can change that by adjusting the outputPath option of the project's build target.

To compile the project each time the code is changed run:

$ ng build PROJECT --watch

Of course, you can also configure a target or configuration in your angular.json and set the watch option to true.

To compile the project and run the built project in a Node.js process each time the code is changed:

$ ng serve PROJECT

Builder options

Builder: build

outputPath: string
Target folder for the built app (relative to the workspace root). Will override compilerOptions.outDir setting of tsconfig.

tsConfig: string
Path to the tsconfig file to use (relative to the workspace root).

watch: boolean
(default: false)
Whether to watch source files for changes and recompile.

cleanOutputPath: boolean
(default: true)
Whether to clean ouputPath before building app.

assets: { input: string, glob: string, output: string, ignore?: string[] }[]
Files to copy to the outputPath. Each asset object has the following properties:

  • input: a path relative to the workspace root
  • glob: a glob relative to input
  • output: a path relative to outputPath
  • ignore: an optional array of globs relative to input

In watch mode (watch set to true) the asset input folders will be watched for changes, i.e. added or modified files. On each change the updated file will be copied.

fileReplacements: { replace: string, with: string }[]
Replace files during compilation. Each array item is an object having the following properties:

  • replace: A file path relative to the workspace root that should be replaced.
  • with: A file path relative to the workspace root that should replace the path specified with replace.

Builder: serve

buildTarget: string
(required)
The build target that uses @da-mkay/ng-builder-typescript builder. It will be started in watch mode. Each time the build target finished compilation successfully, a Node.js process is started that runs the compiled main file.
This options must be a string using the format 'project:build-target[:config]'.

main: string
(required)
The path of the main file relative to the build target's outputPath that will be run using Node.js.

nodeBin: string
The path to the Node.js binary to use. If none is specified the path of the currently running Node.js process is used.

cwd: string
The cwd (current working directory) to use for the spawned Node.js process. If none is specified the build target's outputPath is used.

args: string[]
Arguments to pass to the spawned Node.js process.

Changelog

Check out changelog on Github.