tsdown-migrate

Migrate tsup-based TypeScript libraries to tsdown by transforming configurations and updating dependencies.

3|2|Updated Mar 14, 2023
One-click install
npx skills add https://github.com/2digits-agency/configs --skill tsdown-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tsdown-migrate
Source: https://github.com/2digits-agency/configs/tree/main/.agents/skills/tsdown-migrate
Command: npx skills add https://github.com/2digits-agency/configs --skill tsdown-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Streamlines migrating TypeScript library projects from tsup to tsdown by providing complete option mappings, transformation rules, and default-difference guidance so developers can convert configurations confidently.

Core Features & Use Cases

  • Option Mappings: Translate tsup options to their tsdown equivalents to preserve behavior.
  • Config Transformations: Rename inputs, adjust imports, and apply value changes across config files.
  • Default Differences: Highlight tsup-to-tsdown default changes and how to preserve prior behavior.
  • Package.json Migration: Update dependencies, scripts, and root config fields to tsdown equivalents.
  • Migration Guidance: Help teams plan, validate, and test migrations, with post-migration configuration recommendations.

Quick Start

Initiate a migration by applying the tsup→tsdown mappings to your config and updating package.json accordingly.

Frequently Asked Questions about tsdown-migrate

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

FAQPage Schema
How do I migrate my TypeScript library from tsup to tsdown?

Migrate from tsup to tsdown by mapping options, transforming configurations, updating dependencies, and renaming config files to ensure a safe and consistent transition for your TypeScript package.

What is the best way to convert a tsup config to tsdown?

Convert a tsup config to tsdown by applying complete option mappings, adjusting imports, and highlighting default differences to preserve prior behavior during the config transformation process.

Does migrating from tsup to tsdown change package.json dependencies?

Migrating from tsup to tsdown requires updating package.json dependencies, scripts, and root config fields to their tsdown equivalents to complete the library transition.

Why do my build outputs look different after moving from tsup to tsdown?

Build outputs change because tsdown has different default settings than tsup; you must apply default-difference guidance to adjust configurations and preserve prior behavior.

How are unsupported tsup options handled during a tsdown migration?

Unsupported tsup options are identified and handled during migration to ensure a safe transition, providing guidance on how to manage configurations that lack direct tsdown equivalents.

Can I automate tsup to tsdown migrations across multiple projects?

Automate tsup to tsdown migrations across multiple projects by applying consistent option mappings, config file renames, and package.json updates to cover most migration scenarios.