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

@itwin/build-tools

v5.6.0

Published

Bentley build tools

Readme

@itwin/build-tools

Copyright © Bentley Systems, Incorporated. All rights reserved. See LICENSE.md for license terms and full copyright notice.

Description

The @itwin/build-tools is a package for developers to consolidate the steps for building TypeScript-based packages. The tools contained in this package are written in either Typescript or Javascript within the src/ directory, and compiled for use into the lib/ directory. As a developer package, this package has only dependencies, no devDependencies.

tsconfig-base

Location: tsconfig-base.json
Requires build: no

This file contains common tsconfig settings across all iTwin.js packages. Packages should extend this file in their own tsconfig.json file, and then overwrite and set new properties as needed. Note that this file is different from the tsconfig.json file for this package, as that contains different settings for bentleyjs-tools only.

NPM Scripts

Location: scripts/
Requires build: no

The following node scripts are delivered in this package's scripts folder in order to ease development of iTwin.js packages with npm scripts. These scripts may require that additional packages be installed as dependencies of your package.

The default behaviors of the scripts (without parameters) assume that the directory structure of your package mirrors the following:

  • root
    • source
      • test
        • assets
    • lib
    • package.json
    • tsconfig.json

If the directory structure for your package varies from this, define the NODE_PROJECT_ROOT_DIRECTORY environment variable (The RUSHSTACK_FILE_ERROR_BASE_FOLDER that also serves this function is deprecated) as the path to the directory containing your package.json file.

The following is a list of some of the most commonly used scripts within this package:

docs.js

This script runs a TypeDoc command, with specific parameters, to generate html TypeScript documentation as well as a json representation of the documentation to be consumed for other purposes. It includes the following parameters:

  • source - specify the TypeScript source directory
  • out - specify the directory of the html output
  • json - specify the directory and filename of the json output
  • baseUrl - specify a baseUrl to resolve modules
  • onlyJson - including this option will skip the html output and only output the json file
  • includes - directory of files to include in documentation (ex: for sample code)
  • excludes - name of directory, files, or file extensions to exclude.
    • A list can be provided using a , as a separator
    • Each of the provided to exclude is added to a glob pattern which checks all directories within the source.
      • i.e --excludes=test,docs/*.md will translate to **/{test,docs/*.md}/**/*

extract.js

This is a script designed to extract sample code from test.ts files in a specific directory. The sample code should be surrounded by comments containing "__PUBLISH_EXTRACT_START__" and "__PUBLISH_EXTRACT_END__" directives.

  • extractDir - the path at which the sample code files are located
  • outDir - the path at which to output the selected code

pseudolocalize.js

This script handles translating an English localization JSON file into a pseudoLocalization file.