Update tsdown 0.18.4 → 0.19.0 (major) #117
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
depfu
bot
force-pushed
the
depfu/update/pnpm/tsdown-0.19.0
branch
from
a37c3bf to
a70598e
Compare
buenos-nachos
approved these changes
Jan 23, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ tsdown (0.18.4 → 0.19.0) · Repo
Release Notes
0.19.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 38 commits:
chore: release v0.19.0test: expect warning messageschore: upgrade depsdocs: update `outputOptions.comments` to `legalComments` (#702)feat: clear console on rebuild startfix(cjs): update version check for require ESM supportrefactor(shims): improve shim file path resolution (#700)chore: release v0.19.0-beta.5feat: upgrade rolldown to 1.0.0-beta.59feat: expose `resolveUserConfig`fix(attw): add `--ignore-scripts` to avoid lifecycle output (#661)refactor: enable `pluginTimings` on debugchore: release v0.19.0-beta.4feat: expose `enableDebug`chore(deps): update all non-major dependencies (#677)refactor: expose `buildWithConfigs` (#693)chore: release v0.19.0-beta.3feat(migrate): add monorepo support (#659)feat!: remove deprecated `silent` optionfix: print blank line only when the log level is info (#689)refactor: reorganize importsrefactor(css): splitting pluginrefactor: re-organize cssperf: optimize hot pathschore: release v0.19.0-beta.2feat(exports)!: only auto-fill `types` when `exports.legacy` (#685)fix(exports)!: exclude extension name for `exports.exclude`ci: add build to auto fixchore: release v0.19.0-beta.1feat(exports)!: add `legacy` option, remove `main` & `module` fields if pure ESMfeat!: rename `debugLogs` to `debug`feat(devtools)!: rename `debug` to `devtools`, rename `debug.devtools` to `devtools.ui`feat: upgrade rolldown to 1.0.0-beta.58refactor: fix `resolvePaths` on windowsfeat: generate CSS exports when `css.splitting` is disabled (#680)refactor(config): improve resolving css optionfeat: add `typeAssert` util backdocs: fix link to Rolldown config options (#678)Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands