chore: update build tooling (@swc/core, tsdown, tsx)

[jaredwray]

Please check if the PR fulfills these requirements

• Followed the Contributing and Code of Conduct guidelines.
• Tests for the changes have been added (for bug fixes/features) with 100% code coverage. (Dependency-only change — coverage unchanged at 100%.)

What kind of change does this PR introduce?

Chore — dependency maintenance (build/transform tooling). Part of an ecosystem-clustered dependency update split.

Updates (minor/patch, within existing ranges)

Package	From	To
@swc/core	1.15.41	1.15.43
tsdown	0.22.2	0.22.4
tsx	4.22.4	4.23.0

Grouped as the TypeScript build/transform toolchain. Note tsdown stays at 0.22.4 (the newest release older than the repo's 7-day minimumReleaseAge window); this keeps the declared typescript peer range at ^5 || ^6, which is why the TypeScript 7 bump is being handled separately later.

Verification

• pnpm build (tsdown) — passing
• pnpm test (Biome lint + Vitest) — 473 tests passing across 43 files, coverage 100% lines/functions

---

🤖 Generated with Claude Code

https://claude.ai/code/session_01FjTirhzhuv9RYiVwgjjf3x

---

Generated by Claude Code

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	tsx@​4.23.0
	tsdown@​0.22.4
	@​swc/​core@​1.15.43

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @emnapi/runtime is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/tsdown@0.22.4 → npm/@emnapi/runtime@1.11.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/runtime@1.11.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (556fad6) to head (84f7265).

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #167   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           41        41           
  Lines         1310      1310           
  Branches       259       259           
=========================================
  Hits          1310      1310           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gemini-code-assist]

Code Review

This pull request updates several development dependencies in package.json and their corresponding resolutions in pnpm-lock.yaml, including updates to @swc/core, tsdown, and tsx. There are no review comments, and I have no feedback to provide.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 84f7265c0f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid pinning tsdown before release-age window

As of July 18, 2026, the npm package page reports tsdown@0.22.4 was published only a few hours ago, but this repo sets minimumReleaseAge: 10080 and minimumReleaseAgeStrict: true in pnpm-workspace.yaml; pnpm docs say the age check applies to all dependencies and pnpm install re-applies it to every loaded lockfile entry unless trustLockfile is enabled (https://pnpm.io/settings#minimumreleaseage). I checked .github/workflows/tests.yaml:29 and the other workflows, and they all do fresh pnpm install --frozen-lockfile, so this bump rejects clean CI installs until the package is at least seven days old; keep the old range/resolution or add a deliberate age exception.

Useful? React with 👍 / 👎.