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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@yume-chan/ts-package-builder

v1.0.0

Published

## Installation

Downloads

5

Readme

TypeScript NPM Package Builder (for myself)

Installation

(This package is not yet published to NPM registry, so presumably)

$ npm install --dev @yume-chan/ts-package-builder typescript

TypeScript is a peer dependency that must be installed separately (so you can use any version you want).

$ npm install tslib

The default configuration has "importHelpers": true, so tslib is required (and it is a production dependency, not dev dependency).

Config

A tsconfig.json file at package root is required for both this builder and editors.

{
    // Extends default configurations.
    "extends": "./node_modules/@yume-chan/ts-package-builder/tsconfig.base.json",

    // (Optional) Add override configurations.
    "compilerOptions": {
        // All TypeScript configurations are allowed.
        "target": "ES2016",

        // Add extra ambient types.
        // Don't forget to include "jest" unless you don't write unit tests.
        // The default is `[ "jest" ]`
        "types": [
            "w3c-web-usb",
            "jest",
            "node"
        ]
    },
    // (Optional) Specify types that's only used in tests.
    // They will be excluded in ESModule build,
    // to make sure library code doesn't accidentally use them.
    // (for example, a browser targeted libraries should not use types from `@types/node`)
    "testTypes": [
        "jest",
        "node"
    ],
    // (Optional) Add project references to improve editing experience.
    // However, because the builder is intended to be used with some monorepo manager
    // (lerna, yarn workspace, rush, etc.), and they all have good built-in support
    // for building all packages following dependency graph, it **does not** use
    // project references when building.
    "references": [
        {
            "path": "../dependency-a/tsconfig.json"
        },
        {
            "path": "../dependency-b/tsconfig.json"
        }
    ]
}

Building

$ npx build-ts-package

Or add a script to package.json

{
    "scripts": {
        "build": "build-ts-package",
    },
}

The builder compiles for both CommonJS and ESModule, also generates source maps, TypeScript declarations, and declaration maps.

| Module | Output Directory | Excluded Files | Excluded Types | | ------------------ | ---------------- | -------------- | -------------- | | CommonJS | cjs | - | - | | ESModule | esm | *.spec.ts | @types/jest | | Declaration (d.ts) | dts | *.spec.ts | @types/jest |

Example package.json:

{
    "main": "cjs/index.js",
    "module": "esm/index.js",
    "types": "dts/index.d.ts",
}

Unit test with Jest

Test file convention: put .spec.ts files inside src, alongside the source file that will be tested.

Like this:

  • src
    • index.ts
    • index.spec.ts

The .spec.ts files will be compiled to CommonJS for Jest (so no ts-jest required).

Use the following jest.config.js file to find them:

module.exports = {
    testMatch: ['<rootDir>/cjs/**/*.spec.js'],
};

Publishing

Because .spec.ts files have been compiled to CommonJS, you can exclude them using .npmignore:

**/*.spec.ts
**/*.spec.js
**/*.spec.js.map