skills.rest
prisma
prismaOFFICIAL
Explore all skills by this author →
Website𝕏@prismaGitHub

tsdown-package

Migrate monorepo packages from tsup to tsdown with configuration and build script updates.

419|15|Updated Oct 31, 2025
Search Tags:#typescript#migration#monorepo#build tools#tsdown#tsup
One-click install
npx skills add https://github.com/prisma/prisma-next --skill tsdown-package
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tsdown-package
Source: https://github.com/prisma/prisma-next/tree/main/.claude/skills/tsdown-package
Command: npx skills add https://github.com/prisma/prisma-next --skill tsdown-package

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the migration of monorepo packages from the tsup build tool to tsdown, ensuring a smooth transition with minimal disruption.

Core Features & Use Cases

  • Automated Migration: Converts tsup.config.ts to tsdown.config.ts and updates build scripts.
  • Convention-Based Exports: Leverages auto-generated package.json#exports for consistency.
  • Contract Verification: Ensures public import paths and build outputs remain stable post-migration.
  • Use Case: When instructed to migrate a package like @prisma/sdk from tsup to tsdown, this skill will handle the configuration changes, build process, and verification steps.

Quick Start

Use the tsdown-package skill to migrate the current package from tsup to tsdown.

Frequently Asked Questions about tsdown-package

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a monorepo package from tsup to tsdown?▼

Migrating from tsup to tsdown involves converting tsup.config.ts to tsdown.config.ts and updating package build scripts. The process automates configuration changes and verifies package contracts, public import paths, and build outputs to ensure stability post-migration.

What is the best way to switch TypeScript build tools in a monorepo without breaking imports?▼

Switching TypeScript build tools requires verifying package contracts and public import paths. Using an automated migration to tsdown leverages convention-based exports and validates build outputs to ensure public import paths remain stable and prevent disruptions.

Can I use tsdown for building TypeScript projects that currently rely on tsup?▼

Yes, tsdown can replace tsup for building TypeScript projects. The migration process converts your existing tsup configuration to tsdown and updates build scripts, specifically targeting packages within a monorepo that currently utilize tsup.

Does migrating to tsdown automatically update package.json exports?▼

Migrating to tsdown leverages convention-based, auto-generated package.json exports for consistency. This ensures that your public import paths and build outputs remain stable and correctly configured throughout the migration process.

What are the limitations of migrating from tsup to tsdown?▼

The migration targets monorepo packages currently using tsup. You must verify package contracts, public import paths, and build outputs post-migration to ensure stability, as the process applies specifically to packages within a monorepo environment.

Related Skills

Explore More Software Engineering Skills→
pohlai88pohlai88

ts-tsup-config

Diagnose and govern TypeScript and tsup configurations in the AFENDA-NEXUS monorepo.

Community
Advanced
alex-tgkalex-tgk
1

Verification Before Completion

Execute verification commands to validate tests, lint, and builds before commits.

Community
Advanced
DevHive1DevHive1
18

pnpm-workspace

Enforce pnpm workspace rules and cross-package dependency standards in TypeScript monorepos.

Community
Advanced
seanmcquaidseanmcquaid
8

arch-tsdown

Create ESM TypeScript libraries with tsdown builds and Vitest tests.

Community
Advanced