CLI Reference

Installation

Srcpack runs without global install:

npm

npx srcpack [command] [options]

bun

bunx srcpack [command] [options]

pnpm

pnpm dlx srcpack [command] [options]

yarn

yarn dlx srcpack [command] [options]

Or install as a dev dependency:

npm

npm install -D srcpack

bun

bun add -D srcpack

pnpm

pnpm add -D srcpack

yarn

yarn add -D srcpack

Commands

srcpack (default)

Bundle all configured bundles and upload if configured.

npm

npx srcpack

bun

bunx srcpack

pnpm

pnpm dlx srcpack

yarn

yarn dlx srcpack

With specific bundles:

npm

npx srcpack web api

bun

bunx srcpack web api

pnpm

pnpm dlx srcpack web api

yarn

yarn dlx srcpack web api

Changed files only:

npx srcpack --staged          # staged changes
npx srcpack --dirty           # staged + unstaged + untracked
npx srcpack --since main      # everything you changed since main

These build a one-off bundle from the current change set and need no config file — handy for handing a work-in-progress to an LLM. The bundle is named after the flag (.srcpack/staged.txt), other bundles in outDir are left alone, and nothing is written when there are no changes.

Ad-hoc bundles stay local: they are never uploaded, even with Google Drive configured. Declare a named bundle to publish changes.

For a permanent version with review instructions attached, put a git source in your config instead.

srcpack init

Create a srcpack.config.ts interactively.

npm

npx srcpack init

bun

bunx srcpack init

pnpm

pnpm dlx srcpack init

yarn

yarn dlx srcpack init

Detects your project structure and suggests bundle configurations.

srcpack login

Authenticate with Google Drive for uploads.

npm

npx srcpack login

bun

bunx srcpack login

pnpm

pnpm dlx srcpack login

yarn

yarn dlx srcpack login

Opens a browser to authorize access. Tokens are stored in ~/.config/srcpack/credentials.json, readable only by you.

Options

Option	Description
--staged	Bundle staged changes only
--dirty	Bundle staged, unstaged, and untracked changes
--since <rev>	Bundle changes since <rev>
--dry-run	Preview bundles without writing files
--emptyOutDir	Empty the output directory before writing
--no-emptyOutDir	Keep what is already in the output directory
--no-upload	Bundle only, skip upload
-h, --help	Show help
-v, --version	Show version

An unrecognized option is an error, not a no-op — --no-uplaod would otherwise upload, and --dry-rnu would write.

Examples

Preview without writing

npm

npx srcpack --dry-run

bun

bunx srcpack --dry-run

pnpm

pnpm dlx srcpack --dry-run

yarn

yarn dlx srcpack --dry-run

Output:

  web   3 files  842 lines
    src/api/routes.ts
    src/index.ts
    src/utils/helpers.ts
  docs  1 file   96 lines
    README.md

Dry run: 2 bundles, 4 files, 938 lines

Each bundle lists the files it would contain, so you can check the shape of a pattern before anything is written; outDir is left alone too. A bundle that declares linear still calls the API — the counts are what it would produce right now, which it can't know offline.

Bundle without upload

npm

npx srcpack --no-upload

bun

bunx srcpack --no-upload

pnpm

pnpm dlx srcpack --no-upload

yarn

yarn dlx srcpack --no-upload

Exit Codes

Code	Meaning
0	Success
1	Error (config, IO, etc)

Config File Locations

Srcpack searches for config in order:

1. srcpack.config.ts
2. srcpack.config.mts
3. srcpack.config.js
4. srcpack field in package.json

Searches from current directory up to filesystem root.

srcpack init writes .ts in an ESM project and .mts otherwise — see Configuration.