Skip to content
Back to skills

Setup Tsup

ASecurity

Set up tsup (esbuild-based bundler) for a TypeScript package. Use when you need single-file bundled output, faster builds, and better startup time for Node.js CLIs or libraries. Covers tsup config, bin entry point, package.json scripts, and keeping tsc for type-checking only.

  • 2 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 10, 2026
developmenttypescriptgobashnodegit

Works with

  • cli

Security analysis

A96/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned September 10, 2026

npx -y skills add krafteq/infraglue --skill setup-tsup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Setup Tsup?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Setup Tsup
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/krafteq-setup-tsup/badge)](https://www.skillsdirectory.com/skills/krafteq-setup-tsup)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: setup-tsup
description: Set up tsup (esbuild-based bundler) for a TypeScript package. Use when you need single-file bundled output, faster builds, and better startup time for Node.js CLIs or libraries. Covers tsup config, bin entry point, package.json scripts, and keeping tsc for type-checking only.
---

# Set Up tsup Build

## Goal

Replace or add `tsup` as the build tool for a TypeScript package. Keep `tsc --noEmit` for type-checking only.

## Why

- Single-file bundled output = 2-5x faster startup (fewer fs reads during module resolution)
- Tree-shakes unused code from dependencies
- esbuild-based = sub-second builds vs multi-second tsc

## Steps

### 1. Install tsup

```bash
pnpm add -D tsup
```

### 2. Create tsup.config.ts

```ts
import { defineConfig } from 'tsup'

export default defineConfig({
  entry: ['src/index.ts'],
  format: ['esm'],
  target: 'node22',
  clean: true,
  splitting: false,
  sourcemap: true,
  dts: false,
  // For CLIs: add shebang
  banner: {
    js: '#!/usr/bin/env node',
  },
  // Native/dynamic deps that shouldn't be bundled
  external: [],
})
```

For libraries (not CLIs), remove the `banner` and consider `dts: true` for declaration files.

### 3. Update package.json scripts

```json
{
  "scripts": {
    "build": "tsup",
    "dev": "tsup --watch",
    "ts:check": "tsc --noEmit"
  }
}
```

### 4. Update bin entry point (CLIs only)

The bin file should point to the tsup output. tsup outputs to `dist/` by default:

- Verify the `bin` field references `dist/index.js` (or `dist/index.mjs`)
- Since tsup adds the shebang via `banner`, the bin file can point directly to the bundled output

### 5. Verify

```bash
pnpm build           # Should produce dist/index.js (single file)
pnpm ts:check        # Type checking still works
node dist/index.js --help  # CLI works (if applicable)
```

### 6. Update .gitignore

Ensure `dist/` is in `.gitignore`.

## Gotchas

- If any dependency uses `__dirname` or `require.resolve`, tsup may need those deps in `external`
- Dynamic `import()` calls are preserved by esbuild — this is fine
- Keep `prepare` or `prepublishOnly` script as `pnpm build` for npm publish workflow
- For ESM packages, ensure `"type": "module"` in package.json

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.