Pack

vp pack builds libraries for production with tsdown.

Overview

vp pack builds libraries and standalone executables with tsdown. Use it for publishable packages and binary outputs. If you want to build a web application, use vp build. vp pack covers everything you need for building libraries out of the box, including declaration file generation, multiple output formats, source maps, and minification.

For more information about how tsdown works, see the official tsdown guide.

Usage

vp pack
vp pack src/index.ts --dts
vp pack --watch

Configuration

Put packaging configuration directly in the pack block in vite.config.ts so all your configuration stays in one place. We do not recommend using tsdown.config.ts with Vite+.

See the tsdown guide and the tsdown config file docs to learn more about how to use and configure vp pack.

Use it for:

• declaration files (dts)
• output formats
• watch mode
• standalone executables

vite.config.ts

import { defineConfig } from 'vite-plus';

export default defineConfig({
  pack: {
    dts: true,
    format: ['esm', 'cjs'],
    sourcemap: true,
  },
});

Standalone Executables

vp pack can also build standalone executables through tsdown's experimental exe option.

Use this when you want to ship a CLI or other Node-based tool as a native executable that runs without requiring Node.js to be installed separately.

vite.config.ts

import { defineConfig } from 'vite-plus';

export default defineConfig({
  pack: {
    entry: ['src/cli.ts'],
    exe: true,
  },
});

See the official tsdown executable docs for details about configuring custom file names, embedded assets, and cross-platform targets.

Executable dependencies

The exe option loads @tsdown/exe at build time. Install it together with a matching top-level tsdown package; Vite+'s bundled tsdown is not exposed as a tsdown package that @tsdown/exe can resolve.

vp install -D @tsdown/exe@0.22.0 tsdown@0.22.0

Use the tsdown version shown by vp env current when installing these dependencies for newer Vite+ releases. Installing only @tsdown/exe can surface as Failed to import module "@tsdown/exe" because the underlying peer import tsdown/internal is unresolved.