Skip to content

chore(deps): update dependency tsdown to ^0.21.0#346

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/tsdown-0.x
Open

chore(deps): update dependency tsdown to ^0.21.0#346
renovate[bot] wants to merge 1 commit intomainfrom
renovate/tsdown-0.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 5, 2026

This PR contains the following updates:

Package Change Age Confidence
tsdown (source) ^0.20.0-beta.3^0.21.0 age confidence

Release Notes

rolldown/tsdown (tsdown)

v0.21.1

Compare Source

   🚨 Breaking Changes

[!IMPORTANT]
If you are using CSS features (e.g., CSS imports), you now need to manually install the @tsdown/css package:

npm install @​tsdown/css -D
# or
pnpm add @​tsdown/css -D

Note: CSS support is still an experimental feature and does not follow SemVer. Breaking changes may occur in any release.

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.21.0

Compare Source

v0.21.0 - Notable Changes

Breaking Changes
Dependency options renamed to deps namespace

The dependency-related options have been moved under a new deps namespace with clearer names:

  • external -> deps.neverBundle
  • noExternal -> deps.alwaysBundle
  • inlineOnly -> deps.onlyAllowBundle
  • skipNodeModulesBundle -> deps.skipNodeModulesBundle

Before:

export default defineConfig({
  external: ['vue'],
  noExternal: ['lodash'],
})

After:

export default defineConfig({
  deps: {
    neverBundle: ['vue'],
    alwaysBundle: ['lodash'],
  },
})

The old options still work but are deprecated and will emit warnings.

failOnWarn default changed from 'ci-only' to false

If you relied on the previous behavior where warnings would fail the build in CI environments, you now need to explicitly set failOnWarn: true or failOnWarn: 'ci-only' in your config.

Node.js < 22.18.0 deprecated

tsdown now emits a deprecation warning when running on Node.js versions below 22.18.0. Plan to upgrade your Node.js version accordingly.

New Features
Experimental Node.js SEA executable bundling (exe)

tsdown can now bundle your TypeScript project into a standalone executable using Node.js Single Executable Applications (SEA). A new @tsdown/exe package provides cross-platform executable building support. See the exe documentation for details.

export default defineConfig({
  exe: true, // or { useCodeCache: true, useSnapshot: true }
})
Full CSS pipeline with @tsdown/css

CSS handling has been reimplemented as a native Rolldown plugin and extracted into the @tsdown/css package, providing a complete CSS pipeline with Lightning CSS and PostCSS support via the css.transformer option. See the CSS documentation for details.

inlinedDependencies field in package.json

When using the exports feature, tsdown now auto-generates an inlinedDependencies field in your package.json, listing dependencies that are bundled into the output.

Object option for customExports

customExports now supports an object format for more fine-grained control over the generated exports field.

Migration Guide
  1. Update dependency options: Rename external -> deps.neverBundle, noExternal -> deps.alwaysBundle, etc.
  2. Check failOnWarn: If you need warnings to fail the build in CI, explicitly set failOnWarn: 'ci-only' or failOnWarn: true.
  3. Upgrade Node.js: Ensure you're running Node.js >= 22.18.0 to avoid deprecation warnings.
Links

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.20.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.20.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.20.1

Compare Source

   🚀 Features
    View changes on GitHub

v0.20.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v0.20.0-beta.4

Compare Source

No significant changes

    View changes on GitHub

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Mar 5, 2026

Deploying clerc-website with  Cloudflare Pages  Cloudflare Pages

Latest commit: 4c5dfbe
Status: ✅  Deploy successful!
Preview URL: https://1c4b23ad.clerc-website.pages.dev
Branch Preview URL: https://renovate-tsdown-0-x.clerc-website.pages.dev

View logs

@renovate renovate bot added the renovate label Mar 5, 2026
@pkg-pr-new
Copy link

pkg-pr-new bot commented Mar 5, 2026

Open in StackBlitz

@clerc/advanced-types

npm i https://pkg.pr.new/@clerc/advanced-types@346

clerc

npm i https://pkg.pr.new/clerc@346

@clerc/core

npm i https://pkg.pr.new/@clerc/core@346

@clerc/parser

npm i https://pkg.pr.new/@clerc/parser@346

@clerc/plugin-completions

npm i https://pkg.pr.new/@clerc/plugin-completions@346

@clerc/plugin-friendly-error

npm i https://pkg.pr.new/@clerc/plugin-friendly-error@346

@clerc/plugin-help

npm i https://pkg.pr.new/@clerc/plugin-help@346

@clerc/plugin-not-found

npm i https://pkg.pr.new/@clerc/plugin-not-found@346

@clerc/plugin-strict-flags

npm i https://pkg.pr.new/@clerc/plugin-strict-flags@346

@clerc/plugin-update-notifier

npm i https://pkg.pr.new/@clerc/plugin-update-notifier@346

@clerc/plugin-version

npm i https://pkg.pr.new/@clerc/plugin-version@346

@clerc/utils

npm i https://pkg.pr.new/@clerc/utils@346

commit: 7b8ad8e

@renovate renovate bot force-pushed the renovate/tsdown-0.x branch from 2675155 to 34e0f90 Compare March 5, 2026 18:38
@renovate renovate bot force-pushed the renovate/tsdown-0.x branch from 34e0f90 to 4c5dfbe Compare March 9, 2026 08:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants