chore(deps): bump tsx to 4.23.13 to silence Node 26 DEP0205

[0xDEnYO]

Which Linear task belongs to this PR?

None — dependency bump, covered by the trivial carve-out in the ticket-linkage metric (.agents/context.md).

Why did I implement it this way?

Running any bunx tsx script on Node 26 prints:

(node:19518) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

The call is not ours — git grep module.register across the repo returns nothing. It comes from tsx 4.21.0's ESM loader; Node 26 deprecated module.register() as DEP0205. tsx 4.23.13 no longer uses it, so the warning is gone.

Blast radius is local only. CI never saw this warning: the workflows run under bun, and the two that use Node pin node-version: 20 (jsonChecker.yml, updateLouperViem.yml), where DEP0205 does not exist. This is purely noise reduction for local script runs and agent sessions.

Transitive change: tsx widened its esbuild range from ~0.27.0 to ~0.28.0, so the lockfile also moves esbuild 0.27.7 → 0.28.2 plus its 26 platform-specific optional packages. Nothing else in bun.lock changes — the diff is exactly tsx, esbuild, and those 26 @esbuild/* entries.

Verification

• Reproduced the warning on tsx 4.21.0 and confirmed its absence on 4.23.13, same script, same Node 26.7.0.
• Loaded script/utils/deploymentHelpers.ts (pulls in viem) under both versions — identical behaviour, no transpile drift.
• Ran a real repo task end-to-end (tasks/buildClearSigningProposal.ts) under 4.23.13; it executed and hit its own forge build precondition guard as expected.
• Lockfile regenerated with bun install --lockfile-only so the shared node_modules symlink was left untouched.

Checklist before requesting a review

• I have performed a self-review of my code
• This pull request is as small as possible and only tackles one problem
• I have added tests that cover the functionality / test the bug
• For new facets: I have checked all points from this list: https://www.notion.so/lifi/New-Facet-Contract-Checklist-157f0ff14ac78095a2b8f999d655622e
• I have updated any required documentation

Checklist for reviewer (DO NOT DEPLOY and contracts BEFORE CHECKING THIS!!!)

• I have checked that any arbitrary calls to external contracts are validated and or restricted
• I have checked that any privileged calls (i.e. storage modifications) are validated and or restricted
• I have ensured that any new contracts have had AT A MINIMUM 1 preliminary audit conducted on by <company/auditor>

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

Next included review available in 16 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Advanced

Run ID: 2d33c425-c669-47f6-8065-ae06c39574d1

📥 Commits

Reviewing files that changed from the base of the PR and between ba03e2b and 7705ac6.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• package.json

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[0xDEnYO]

@coderabbitai review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.