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

@davidmz/ts-lib-build

v0.3.2

Published

A builder for the small TypeScript libraries based on 'unbuild'

Readme

@davidmz/ts-lib-build

An opinionated builder for the small TypeScript libraries based on 'unbuild'.

This builder compiles the .ts sources into .cjs and .mjs files and copies them to the build (configurable) folder. It creates a package.json in that folder without the unneeded fields (like 'devDependencies' or 'scripts') and adds proper 'exports' field. See below for more information.

Requirements to project

You code expected to be in the src folder. The entry point should be index.ts as well as the entry point of exported sub-folders.

The readme file should be README.md and the license file should be LICENSE.txt.

The homepage field in the package.json should be set to use the "trimReadme" feature.

It is recommended to use the publishConfig.directory entry in the package.json file. It will be used as the build folder and simplify the publish process (you will only need to run npm publish).

Install it using npm/yarn/pnpm as @davidmz/ts-lib-build and run the ts-lib-build command to build.

Configuration

The builder can work without the configuration file. By default, it will build the src/index.ts to the one file and create the output in the publishConfig.directory, when specified in package.json. If it is not specified, the build will be placed in the build folder.

You can create an explicit configuration file named ts-lib-build.config.json in the project root. The file structure is as follows (all fields are optional):

{
  // The directory where the build will be placed.
  "buildDir": "build", // default: `publishConfig.directory` or `build`

  // The list of sub-folders to export. Empty string means the `src`
  // folder itself.
  "dirsToExport": [""],

  // Whether to trim the README.md file or include it as is.
  "trimReadme": true,

  // The list of additional fields to copy from the package.json to the 
  // build folder's package.json. Some fields are always copied, see below.
  "fieldsToCopy": []
}

The always copied fields of the package.json are:

  • "name"
  • "version"
  • "description"
  • "homepage"
  • "author"
  • "license"
  • "sideEffects"
  • "dependencies"
  • "peerDependencies"