Skip to content

chore(deps): update dependency tsdown to ^0.22.0#11

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

chore(deps): update dependency tsdown to ^0.22.0#11
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/tsdown-0.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jan 23, 2026 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
tsdown (source) ^0.19.0-beta.3 → ^0.22.0 age confidence

Release Notes

rolldown/tsdown (tsdown)

v0.22.0

Compare Source

   🚨 Breaking Changes
  • Drop Node.js < 22.18.0 support, make unrun optional, add tsx config loader  -  by @​sxzz (a1042)
  • dts: Auto-enable dts when tsconfig declaration is true  -  by @​sxzz in #​872 (085f0)
  • publint: Use pkg from publint results, require publint v0.3.8+  -  by @​sxzz (413bb)
   🚀 Features
   🐞 Bug Fixes

🔄 Migration Guide

Node.js version

Upgrade to Node.js 22.18.0 or later. Bun and Deno remain supported (experimental).

unrun is no longer bundled

If your environment relies on the unrun config loader (i.e. you're on a Node version without native TypeScript support and use the default auto loader), install it manually:

npm i -D unrun

# or, alternatively, the new tsx loader:
npm i -D tsx

If you use Node.js 22.18.0+ with native TypeScript support, no change is needed — the auto loader will pick native.

dts auto-enabled from tsconfig

If your tsconfig.json has compilerOptions.declaration: true but you do not want tsdown to emit .d.ts files, opt out explicitly:

// tsdown.config.ts
export default defineConfig({
  dts: false,
})
exports.bin auto-detection

Any entry chunk containing a shebang (e.g. #!/usr/bin/env node) now causes tsdown to write a bin field in package.json automatically. The semantics differ slightly from explicit bin: true:

Value Single shebang Multiple shebangs No shebangs
(unset) Auto-set bin Warn, skip Silent
true Auto-set bin Throw Warn
false No bin No bin No bin

To opt out entirely:

export default defineConfig({
  exports: { bin: false },
})
Links

v0.21.10

Compare Source

   🚀 Features
    View changes on GitHub

v0.21.9

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.21.8

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.21.7

Compare Source

   🚀 Features
  • Add module option for attw and publint to allow passing imported modules directly  -  by @​sxzz (31e90)
   🐞 Bug Fixes
  • deps: Add skipNodeModulesBundle dep subpath e2e tests and fix docs  -  by @​sxzz (deff7)
    View changes on GitHub

v0.21.6

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.21.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.21.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
  • exports: Preserve CRLF line endings in package.json  -  by @​sxzz (a4d4e)
    View changes on GitHub

v0.21.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.21.2

Compare Source

   🚨 Breaking Changes
  • exe: Add exe.outDir for separate executable output dir, defaults to build  -  by @​sxzz (d49ef)

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

   🚀 Features
   🐞 Bug Fixes
  • css: Skip data URIs and external URLs in CSS url() rebasing  -  by @​sxzz (13907)
    View changes on GitHub

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 @&#8203;tsdown/css -D
# or
pnpm add @&#8203;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

Configuration

📅 Schedule: (UTC)

  • 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.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Jan 23, 2026 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 15, reused 0, downloaded 0, added 0
Progress: resolved 16, reused 0, downloaded 0, added 0
Progress: resolved 126, reused 0, downloaded 0, added 0
Progress: resolved 189, reused 0, downloaded 0, added 0
 ERR_PNPM_TRUST_DOWNGRADE  High-risk trust downgrade for "semver@5.7.2" (possible package takeover)

This error happened while installing the dependencies of @vscode/vsce@3.7.1
 at parse-semver@1.1.1

Trust checks are based solely on publish date, not semver. A package cannot be installed if any earlier-published version had stronger trust evidence. Earlier versions had provenance attestation, but this version has no trust evidence. A trust downgrade may indicate a supply chain incident.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Jan 23, 2026 •
edited
Loading

⚠️ No Changeset found

Latest commit: 6b91924

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jan 23, 2026

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Comment @coderabbitai help to get the list of available commands and usage tips.

ellipsis-dev[bot]
ellipsis-dev Bot reviewed Jan 23, 2026
View reviewed changes
Copy link
Copy Markdown

@ellipsis-dev ellipsis-dev Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

Looks good to me! 👍

Reviewed everything up to 8c52d3a in 39 seconds. Click for details.
  • Reviewed 13 lines of code in 1 files
  • Skipped 0 files when reviewing.
  • Skipped posting 1 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. package.json:361
  • Draft comment:
    Updated tsdown to ^0.20.0. Please verify that any breaking changes (e.g. removal of the 'dts.resolve' option) in tsdown v0.20.0 don't impact the build configuration.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to verify potential breaking changes in a dependency update, which violates the rule against asking the author to ensure the behavior is intended or to double-check things. It does not provide a specific suggestion or point out a specific issue.

Workflow ID: wflow_U2ocnz36gZcdtaqq

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

@renovate renovate Bot force-pushed the renovate/tsdown-0.x branch from 8c52d3a to ec74fe6 Compare March 8, 2026 06:47
@renovate renovate Bot changed the title chore(deps): update dependency tsdown to ^0.20.0 chore(deps): update dependency tsdown to ^0.21.0 Mar 8, 2026
@renovate renovate Bot force-pushed the renovate/tsdown-0.x branch from ec74fe6 to 6b91924 Compare May 7, 2026 14:14
@renovate renovate Bot changed the title chore(deps): update dependency tsdown to ^0.21.0 chore(deps): update dependency tsdown to ^0.22.0 May 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ellipsis-dev ellipsis-dev[bot] ellipsis-dev[bot] left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants