[dependabot]

Bumps the development-dependencies group with 16 updates in the / directory:

Package	From	To
@changesets/cli	3.0.0	3.0.3
@playwright/test	1.61.1	1.64.1
@tanstack/intent	0.3.6	0.5.5
@vitejs/plugin-vue	6.0.1	6.0.10
concurrently	9.2.4	9.2.5
supabase	2.112.0	2.121.0
wrangler	4.114.0	4.151.0
tsdown	0.22.13	0.23.1
@tsconfig/node22	22.0.2	22.0.6
sass-embedded	1.90.0	1.105.2
unocss	66.7.5	66.11.0
vite	7.3.6	7.3.7
vite-plugin-vue-devtools	8.0.0	8.2.1
@unocss/preset-uno	66.7.5	66.11.0
sass	1.101.6	1.105.2
wxt	0.20.27	0.21.4

Updates @changesets/cli from 3.0.0 to 3.0.3

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​3.0.3

Patch Changes

• #2297 3f163da Thanks @​Andarist! - Fixed semver ranges (such as >=1.0.0 <2.0.0) getting cut off (>=2.0.0) when updating internal dependencies.

• #2276 ca9d110 Thanks @​Andarist! - Fixed pnpm 10 compatibility with npm 12 when reading registry information, packing, and publishing packages.

• Updated dependencies [3f163da, bfe9050, e522996]:

  • @​changesets/apply-release-plan@​8.1.1
  • @​changesets/config@​4.0.1

@​changesets/cli@​3.0.2

Patch Changes

• #2270 a0a4dc6 Thanks @​bluwy! - Add review message on pre exit
• Updated dependencies [1f4eb61, 059f70a]:
  • @​changesets/apply-release-plan@​8.1.0
  • @​changesets/git@​4.0.1
  • @​changesets/read@​1.0.1

@​changesets/cli@​3.0.1

Patch Changes

• #2239 fdfdc93 Thanks @​bluwy! - Update links in default generated .changeset/README.md file
• Updated dependencies [d0386b6]:
  • @​changesets/write@​1.0.1

Changelog

Sourced from @​changesets/cli's changelog.

3.0.3

Patch Changes

• #2297 3f163da Thanks @​Andarist! - Fixed semver ranges (such as >=1.0.0 <2.0.0) getting cut off (>=2.0.0) when updating internal dependencies.

• #2276 ca9d110 Thanks @​Andarist! - Fixed pnpm 10 compatibility with npm 12 when reading registry information, packing, and publishing packages.

• Updated dependencies [3f163da, bfe9050, e522996]:

  • @​changesets/apply-release-plan@​8.1.1
  • @​changesets/config@​4.0.1

3.0.2

Patch Changes

• #2270 a0a4dc6 Thanks @​bluwy! - Add review message on pre exit
• Updated dependencies [1f4eb61, 059f70a]:
  • @​changesets/apply-release-plan@​8.1.0
  • @​changesets/git@​4.0.1
  • @​changesets/read@​1.0.1

3.0.1

Patch Changes

• #2239 fdfdc93 Thanks @​bluwy! - Update links in default generated .changeset/README.md file
• Updated dependencies [d0386b6]:
  • @​changesets/write@​1.0.1

Commits

• c9269c0 Version Packages (#2291)
• ca9d110 Fix pnpm 10 publishing with npm 12 (#2276)
• 7be7fde Build(deps): Bump the production-dependencies group across 1 directory with 6...
• b430ce0 Move e2e tests to an on-demand workspace (#2275)
• 93314a8 test: add happy path tests for add (#2289)
• d13a39e test: use inline snapshots for publish plan tests (#2284)
• d7e4a2d Version Packages (#2266)
• 68affee Upgrade to Vitest 5 (#2281)
• 5eeb012 Build(deps): Bump human-id in the production-dependencies group (#2279)
• a0a4dc6 Add review message on pre exit (#2270)
• Additional commits viewable in compare view

Updates @playwright/test from 1.61.1 to 1.64.1

Release notes

Sourced from @​playwright/test's releases.

v1.64.1

Bug Fixes

• #43247 [Bug]: _electron.launch intermittently loses a packaged app's first window since 1.64.0
• #43242 [Regression]: Chromium 155+ aborts a preflighted cross-origin redirect whenever any route is registered (net::ERR_ABORTED)

v1.64.0

🧰 WebMCP

New page.webmcp and frame.webmcp give access to the tools that a page registers through the experimental WebMCP browser API, so you can test them like any other part of your app:

const browser = await chromium.launch({ args: ['--enable-features=WebMCP'] });
const page = await browser.newPage();
await page.goto('https://example.com');
for (const tool of await page.webmcp.tools())
console.log(tool.name, tool.description);
const result = await page.webmcp.callTool('add', { a: 2, b: 40 });
console.log(result.content[0].text); // "42"

Playwright MCP also supports WebMCP by default, with page-defined tools offered to the agent as webmcp_<tool>. Pass --no-webmcp to opt out.

playwright-cli exposes them as well:

playwright-cli webmcp-list
playwright-cli webmcp-call search_catalog --params '{"query":"cats"}'

🎬 Better videos

Videos can now be recorded at a custom frame rate, and the decorations for actions are styled with plain CSS:

// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
use: {
video: {
mode: 'on',
size: { width: 1920, height: 1080 },
fps: 60,
show: {
actions: {
style: {
point: 'width: 20px; height: 20px; border-radius: 50%; background: red',
</tr></table>

... (truncated)

Commits

• cfe490d cherry-pick(#43353): docs: release notes for v1.64 Python
• 866cbb8 chore: mark v1.64.1 (#43354)
• 1b29247 cherry-pick(#43250): fix(electron): do not drop windows that have not navigat...
• 632d976 cherry-pick(#43249): fix(chromium): disable AvoidCorsURLLoaderRestartOnRedirect
• 824d0c5 cherry-pick(#43217): chore(dotnet): fix async suffix of optional-arg overload...
• 606ecd8 cherry-pick(#43192): fix(locators): parse locators the way the client API bui...
• e4f872c cherry-pick(#43188): feat(api): expose asLocatorDescription via LocalUtils fo...
• f6a439e cherry-pick(#43189): docs(webmcp): expose WebMCP to all languages
• e2335c3 cherry-pick(#43174): fix(mcp): do not close the browser twice when the client...
• d2a436e cherry-pick(#43163): Revert "fix(blob): do not remove existing reports from o...
• Additional commits viewable in compare view

Updates @tanstack/intent from 0.3.6 to 0.5.5

Release notes

Sourced from @​tanstack/intent's releases.

@​tanstack/intent@​0.5.5

Patch Changes

• #330 0365fc6 - Leave a SKILL.md that review.ignore matches out of the skills that review and maintainer setup discover. A Claude Code plugin kept beside the library, such as plugins/<name>/skills/, was reviewed as a library skill and reported No source paths declared, and maintainer setup registered it. A skill that the tree declares is still reviewed.

@​tanstack/intent@​0.5.4

Patch Changes

• #324 755bd33 - Make the installed package 28 kB smaller by bundling yaml from its ES module build instead of its CommonJS build. A YAML warning, such as an unresolved tag in skill frontmatter, is now written to stderr by console.warn, with a stack trace; before, it went through process.emitWarning, and intent list and intent stale exited before Node printed it. The LOG_STREAM and LOG_TOKENS environment variables no longer make the YAML parser print its tokens to stdout.

• #322 71cd72c - Start each command faster. The command-line parser processed the arguments one time for each registered command; Intent now gives it only the command being run. A call saves between 0.1 and 0.2 ms.

• #314 29ac2d1 - Print the installed version for intent --version. The CLI had no version flag, so it printed the help text and exited with code 1. It now prints the version alone and exits with code 0.

• #325 594fd9d - Stop shipping a type declaration file for the CLI entry. Nothing could import dist/cli.d.mts, so the installed package is 2,655 bytes smaller. The types for @tanstack/intent and @tanstack/intent/core do not change.

• #319 9d8a463 - Add fence properties that control how intent validate checks one code example. no-check after the language skips a fragment that is not a complete source file. expect-error requires the example to report an error, and expect-error=TS2322 requires that error code, so a deliberately wrong example fails validation once it compiles.

• #326 cd5a024 - Write the command parser in the hook script as fixed text, so the script content no longer changes with the build tooling. Hook behavior does not change. The next intent hooks install rewrites the installed script once and reports Updated Intent hooks; later runs report no changes.

• #313 39d2af8 - Allow workspace packages to register skills with the same name. intent maintainer commands failed with Duplicate skill identity or path in a monorepo where two packages each had, for example, a getting-started skill; a skill name is now unique within its owning package, a prerequisite name refers to a skill in the same package, and maintainer remove <name> accepts --package <directory> when more than one package registers the name.

• #317 894ab61 - Recognize a skill_tree.yaml entry whose path repeats its package directory. intent maintainer status and check reported every such skill as Missing skill although the file existed; they now find the skill and list the tree as a file to synchronize, and intent maintainer sync rewrites the path relative to the package.

• #315 f7619bf - Report intent.skills entries that name a skill the package does not ship. An exact entry such as @tanstack/query#fetching yielded no skill and no message when the installed package had removed or renamed that skill; Intent now reports the entry as not discovered.

• #323 5a0ec60 - Make the installed package 35 kB smaller. intent stale now bundles only the semver functions it uses instead of the whole library; behavior does not change.

• #310 c16a6a8 - Stop intent stale from reporting artifact library version drift for a skill whose library_version matches the current version of its own package. Monorepos that version packages independently no longer get this false warning, and a review signal raised by more than one artifact file now prints once in the text output.

• #327 a7c93e0 - Make the installed package 16 kB smaller and load fewer files in each command. intent validate and intent stale imported modules a second time through a deferred import, although the same files had already loaded them. Those modules are now imported directly, so the bundle keeps only the parts of yaml that Intent uses; behavior does not change.

• #312 d346d64 - Make intent validate faster in workspaces that check examples for more than one library. The workspace package map is now resolved once per run, and parsed library and TypeScript lib files are reused between libraries instead of being parsed again for each one. Validation results are unchanged.

• #316 9212c2d - validate reports an error when a relative Markdown link in a SKILL.md resolves to a path outside the package that owns the skill, even when the target exists in the repository. Only the package is installed in a consumer project, so such a link is dead for every consumer.

• #318 db658f7 - intent validate now checks every Markdown file under a skill's references/ directory: the file must not begin with frontmatter, the SKILL.md body must link to it directly, and its TypeScript and JavaScript examples are checked with the skill's examples. A skill_tree.yaml entry for a skill with reference files must list them in a references key, and the list must match the files. Existing repositories now fail validation for reference files that SKILL.md does not link to directly, reference frontmatter, reference examples that do not typecheck, and tree entries that do not list their skill's reference files.

@​tanstack/intent@​0.5.3

Patch Changes

• #308 9e4a28d - Check code examples in repositories that use TypeScript 7.0. intent validate, intent repair, and maintainer review summaries crashed there because the TypeScript 7 typescript package exports no compiler API. Intent now checks examples through the native compiler API that TypeScript 7 publishes, or through @typescript/typescript6 when it is installed beside TypeScript 7. If neither API can run, Intent reports that the examples were not typechecked and runs the other checks. TypeScript 7.1 is not supported at this time.

@​tanstack/intent@​0.5.2

Patch Changes

• #305 8948aac - Discover skills on Windows under Node 23 and Node 24.0 through 24.1. Those versions report a zero device id from lstat while the opened descriptor reports the real one, so the skill identity check rejected every skill and intent list and the session catalog reported none even though intent load worked. A zero device id now carries no identity and only the inode is compared.

@​tanstack/intent@​0.5.1

Patch Changes

... (truncated)

Commits

• 683c701 ci: changeset release (#332)
• 0365fc6 fix: leave skills that review.ignore matches out of default discovery (#330)
• 08865b7 ci: changeset release (#311)
• a7c93e0 perf: import already-loaded modules statically (#327)
• cd5a024 fix: write the hook script parser as fixed text (#326)
• 594fd9d perf: emit type declarations for exported entries only (#325)
• 755bd33 perf: bundle yaml from its ES module build (#324)
• 5a0ec60 perf: bundle only the semver functions that stale uses (#323)
• 9212c2d feat: reject skill links that leave the package (#316)
• 71cd72c perf: parse the command line once for the command being run (#322)
• Additional commits viewable in compare view

Updates @vitejs/plugin-vue from 6.0.1 to 6.0.10

Release notes

Sourced from @​vitejs/plugin-vue's releases.

plugin-vue@6.0.10

Please refer to CHANGELOG.md for details.

plugin-vue@6.0.9

Please refer to CHANGELOG.md for details.

plugin-vue@6.0.8

Please refer to CHANGELOG.md for details.

plugin-vue@6.0.7

Please refer to CHANGELOG.md for details.

plugin-vue@6.0.6

Please refer to CHANGELOG.md for details.

plugin-vue@6.0.5

Please refer to CHANGELOG.md for details.

plugin-vue@6.0.4

Please refer to CHANGELOG.md for details.

plugin-vue@6.0.3

Please refer to CHANGELOG.md for details.

plugin-vue@6.0.2

Please refer to CHANGELOG.md for details.

Changelog

Sourced from @​vitejs/plugin-vue's changelog.

6.0.10 (2026-10-10)

Bug Fixes

• plugin-vue: compile transformed normal scripts outside vapor mode (#857) (7b63e3c)
• plugin-vue: correct AST reuse checks and allow Vue 3.6 RC (ccc06dd)

Documentation

• plugin-vue: clarify compiler initialization hooks (55d0cab)

6.0.9 (2026-09-14)

Bug Fixes

• deps: update all non-major dependencies (#812) (b2b559d)
• plugin-vue: initialize compiler correctly (#475) (127b03f)
• plugin-vue: transpile TS in templates with empty script block (#838) (189148e)

Miscellaneous Chores

• deps: update dependency obug to v3 (#846) (3180192)

6.0.8 (2026-07-14)

Features

• plugin-vue: add forced vapor mode option (#766) (d59c3c0)

Bug Fixes

• deps: update all non-major dependencies (#781) (d369e5a)

6.0.7 (2026-05-15)

Features

• use carets for @rolldown/pluginutils version (#776) (941b651)

Bug Fixes

• deps: update all non-major dependencies (#762) (9e825b8)
• deps: update all non-major dependencies (#774) (77dc8bc)

6.0.6 (2026-04-13)

Features

• plugin-vue: propagate multiRoot for template-only vapor components (#745) (9e07ae9)

Bug Fixes

• deps: update all non-major dependencies (#738) (050c996)

Miscellaneous Chores

... (truncated)

Commits

• a03675e release: plugin-vue@6.0.10
• 7b63e3c fix(plugin-vue): compile transformed normal scripts outside vapor mode (#857)
• ccc06dd fix(plugin-vue): correct AST reuse checks and allow Vue 3.6 RC
• 55d0cab docs(plugin-vue): clarify compiler initialization hooks
• 822c69d release: plugin-vue@6.0.9
• 127b03f fix(plugin-vue): initialize compiler correctly (#475)
• 3180192 chore(deps): update dependency obug to v3 (#846)
• 189148e fix(plugin-vue): transpile TS in templates with empty script block (#838)
• b2b559d fix(deps): update all non-major dependencies (#812)
• d8ff7d0 release: plugin-vue@6.0.8
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​vitejs/plugin-vue since your current version.

Updates concurrently from 9.2.4 to 9.2.5

Release notes

Sourced from concurrently's releases.

v9.2.5

What's Changed

• deps: update shell-quote to 1.12.0 by @​Abicodexi and @​Mayvis in open-cli-tools/concurrently#622

Full Changelog: open-cli-tools/concurrently@v9.2.4...v9.2.5

Commits

• 4fb52e2 9.2.5
• dac54d0 deps: update shell-quote to 1.12.0 (#622)
• See full diff in compare view

Updates supabase from 2.112.0 to 2.121.0

Release notes

Sourced from supabase's releases.

v2.121.0

Supabase CLI v2.121.0 — 2026-10-14

This release is mostly stack reliability fixes, plus new stack options and deprecation warnings you'll want to see before the next major version. Most entries below are from PR titles, not full PR review.

Highlights

• OrioleDB through db.orioledb_version — set the OrioleDB version in config instead of relying on a separate setup path. (#6934)
• Repeatable --stack-id in stack destroy — tear down several stacks in one command. (#6964, #7000)
• Gateway requests show up in Studio — API Gateway logs in Studio now include requests that pass through the local stack gateway. (#6942)

New features

• stack destroy --stack-id accepts multiple IDs — e.g. supabase stack destroy --stack-id a --stack-id b. (#6964, #7000)
• Leftover containers from deleted stacks get cleaned up — stale containers are removed automatically instead of piling up. (#7017)
• Changed endpoint ports apply on restart — if you change endpoint ports while a stack is stopped, the new ports are used the next time it starts. (#6950)
• Deprecation warnings for db pull and domains flags — you now see a warning at runtime when you use a deprecated flag. (#7115)

Improvements

• functions serve defaults to stream-json for agents — when running non-interactively, output is streamed as JSON so agent tooling can parse it. (#7027)
• Heads-up: deprecated config, env vars and import maps will be removed in the next major version — the CLI now warns when you use them. Migrate before upgrading to that major. (#7154)
• Clearer db remote commit and inspect db deprecation messages — the warnings now say the features are removed in the next major version. (#7108)
• More specific failure telemetry — stack and platform failures are classified and named more precisely, which makes issues easier to triage. (#7044, #7113, #7137, #7067)

Bug fixes

• supabase start works with Podman when no snippets are present. (#7089)
• Stack creates the supabase_functions database on the stack backend. (#7029)
• functions serve overrides apply after the stack has started. (#7028)
• Native Postgres trusts your host CA bundle, so connections through corporate or custom certificates work. (#7023)
• Auth database and stack host connections stay alive instead of dropping mid-session. (#7080)
• Gateway writes no longer fail under load, because they reuse keep-alive connections. (#7075, #6981)
• Containers whose host port was taken before start are recreated rather than failing to start. (#7081)
• Database helpers are removed when their owner exits, so they stop leaking between runs. (#7014, #6962)
• Running dependents restart when a prerequisite crashes, so the stack recovers without a manual restart. (#7093)
• pg_cron jobs run in background workers on native Postgres. (#7039)
• Database helpers are created by name before they're attached to. (#7068)
• supabase stop waits for a concurrent Docker prune instead of failing. (#7143, #7129)
• Config accepts the new Management API Postgres settings, so they no longer get rejected. (#7056, #7054, #6934)

---

Plus 1 internal improvement and dependency update.

Full changelog: supabase/cli@v2.120.0...v2.121.0

v2.121.0-next.2

No release notes provided.

... (truncated)

Commits

• 8a549df fix(cli): warn that deprecated config, env vars and import maps are removed i...
• d47510f ci: speed up tests with sticky disks, parallel e2e and on-demand Windows and ...
• d68f6d0 fix(cli): wait for a concurrent Docker prune in stop (#7143)
• ddb5c6e chore(stack): bump storage to v1.82.1-r0 (#7153)
• 2930f6d docs(cli): port pg-delta reference fixes into db diff and db pull overlays (#...
• 45376da fix(cli): name the failing platform operation in defect telemetry (#7137)
• cb2985f chore(cli): map db dump, pull, diff and declarative command permissions (#7136)
• 28dad9c chore(stack): bump storage to v1.82.0-r0 (#7140)
• 87e47b5 chore(cli): map db lint, push, reset and related command permissions (#7135)
• 9af6852 chore(cli): bring the remaining commands under the effect skill (CLI-2693) (#...
• Additional commits viewable in compare view

Updates wrangler from 4.114.0 to 4.151.0

Release notes

Sourced from wrangler's releases.

wrangler@4.151.0

Minor Changes

• #16245 d6b1c82 Thanks @​WalshyDev! - Include source maps by default in wrangler build --experimental-cf-build-output

  Build Output now matches wrangler deploy and wrangler versions upload, which upload source maps by default, so Workers built for tools like cf get stack traces that point at the original source. Source maps that can't be resolved are skipped rather than failing the build. Set upload_source_maps = false to opt out.

Patch Changes

• #16220 97b2fb1 Thanks @​FlorentCollin! - Support local D1 queries through the experimental d1_binding_jsrpc compatibility flag

  Local D1 bindings now implement the RPC query backend used by D1Database.query() and prepared-statement methods when the flag is enabled. Queries reuse local SQLite execution, including transactional batches, execution metadata, and session bookmarks, while bindings without the flag continue to use HTTP. Update the bundled workerd runtime to 1.20261012.1 and align the default compatibility date with that release.

• Updated dependencies [f360829, 97b2fb1, 97b2fb1, acd2822]:

  • miniflare@5.20261012.0-beta

wrangler@4.150.0

Minor Changes

• #16231 091e5ec Thanks @​WalshyDev! - Upload source maps by default for wrangler deploy, wrangler versions upload and wrangler preview

  When upload_source_maps isn't set in config or via --upload-source-maps, Wrangler now generates and uploads source maps so stack traces in logs and wrangler tail point at your original source without extra setup. In this default mode, source maps that can't be resolved (for example inline data: maps or missing .map files from a custom build) are skipped rather than failing the upload. Setting upload_source_maps = true keeps the existing strict behaviour, and upload_source_maps = false (or --no-upload-source-maps for deploy and versions upload) opts out.

  wrangler build --experimental-cf-build-output is unchanged and still only includes source maps when upload_source_maps = true.

• #16128 daae435 Thanks @​redsteadz! - Stop wrangler deploy, wrangler versions upload and wrangler preview in projects that build for the Cloudflare CLI (cf)

  If your project builds through cf, deploying it with Wrangler reads a different configuration, so it could update the wrong Worker or fail without explaining why. These commands now stop before uploading anything, name the .cloudflare/output directory they found, and tell you to run cf deploy instead. If that directory is just left over from an earlier build, deleting it restores the Wrangler workflow.

  Ordinary Wrangler projects are unaffected, and --dry-run still works on deploy and versions upload. This is a new guard for the experimental Build Output Specification rather than a fix, and it gives three stable commands a failure mode they did not have before, so it is a minor.

Patch Changes

• #16161 fcf625d Thanks @​dario-piotrowicz! - Clarify the Worker not found error during CI deploy validation

  Wrangler now reports that the configured Worker could not be found in the account instead of incorrectly describing the failure as a name mismatch.

• #16156 18f061c Thanks @​armancharan! - Ignore .wrangler writes in the dev assets watcher

  wrangler dev reloaded in a loop when assets.directory was the project root, because the assets watcher treated wrangler's own writes under .wrangler as asset changes and dropped in-flight requests. The watcher now ignores the project's .wrangler directory and dev.persist, except when that path is the assets directory.

• #16025 61e07fd Thanks @​kohjunhao! - Fix optional Docker lookups printing Docker CLI errors during successful builds

  cf build looks for Container images left behind by earlier builds so it can remove them. This lookup is best effort, but when Docker could not be reached it still printed errors such as Cannot connect to the Docker daemon, even when the build succeeded and no image needed Docker. Docker commands whose output Wrangler reads no longer forward the Docker CLI's error output to the terminal. If one of these commands fails in a way that stops the command, the error message still includes the Docker CLI's output.

• #16151 cafd3f9 Thanks @​DevVettel! - Time out the OAuth token request instead of waiting indefinitely

  The request that exchanges an authorization code or refresh token for an access token had no timeout, so a stalled connection (for example behind an HTTP proxy) could leave wrangler login hanging silently for many minutes after the browser step had succeeded. The request now gives up after 30 seconds and reports that the Cloudflare auth server could not be reached.

• #15517 ea64ec4 Thanks @​xgame92! - Preserve binding options when provisioning resources through a redirected config

... (truncated)

Commits

• b81efbc Version Packages (#16241)
• d6b1c82 Generate source maps by default for Vite plugin Workers and Build Output (#16...
• fb3d9c8 Version Packages (#16162)
• 091e5ec [wrangler] Upload source maps by default (#16231)
• ea64ec4 [wrangler] Preserve D1 migration paths during redirected provisioning (#15517)
• d232454 [wrangler] Preserve public HTTPS response URLs behind TLS-terminating proxies...
• 18f061c [wrangler] Ignore .wrangler writes in the dev assets watcher (#16156)
• fdd4b53 [wrangler] Fix preview URL warning E2E snapshot (#16213)
• fcf625d Clarify the Worker not found error during CI deploy validation (#16161)
• 794855c [ci] Shorten test critical path and expose flaky retries (#16179)
• Additional commits viewable in compare view

Updates tsdown from 0.22.13 to 0.23.1

Release notes

Sourced from tsdown's releases.

v0.23.1

   🐞 Bug Fixes

• Preserve false tsconfig option  -  by @​Masutayunikon in rolldown/tsdown#1065 (407f8)
• entry: Honor custom root for object entry  -  by @​giaBaoJS in rolldown/tsdown#1072 (17452)
• pkg: Pack tarball inside npm publish --dry-run  -  by @​giaBaoJS in rolldown/tsdown#1076 (83f0c)

    View changes on GitHub

v0.23.0

   🧭 Migration Guide

Most users can upgrade directly. Before upgrading, run one final build with tsdown@0.22.14 and resolve all d...

Description has been truncated