Skip to content

build(deps-dev): bump typescript to 6.0.3 and modernise module resolution - #211

Merged
Eliav2 merged 1 commit into
mainfrom
build/typescript-6
Aug 8, 2026
Merged

build(deps-dev): bump typescript to 6.0.3 and modernise module resolution#211
Eliav2 merged 1 commit into
mainfrom
build/typescript-6

Conversation

@Eliav2

@Eliav2 Eliav2 commented Aug 8, 2026

Copy link
Copy Markdown
Owner

Supersedes #199.

Why #199 cannot be merged on its own

The bump alone fails type-check:

tsconfig.json(16,25): error TS5107: Option 'moduleResolution=node10' is deprecated
and will stop functioning in TypeScript 7.0. Specify compilerOption
'"ignoreDeprecations": "6.0"' to silence this error.

Dependabot cannot make the tsconfig change that goes with it, so its PR is red by construction.

What this does instead

"ignoreDeprecations": "6.0" would silence it and hand the identical error to TypeScript 7. This moves both tsconfigs to module: esnext + moduleResolution: bundler instead, which is simply an accurate description of the project since #204: Vite does the bundling, and the published package resolves through an exports map rather than node10 directory walking.

Risk

None to the shipped artifact. tsc no longer emits any JavaScript here, only declarations through vite-plugin-dts.

Confirmed rather than assumed: built main and this branch and diffed lib/.

  • no differences outside sourcemaps
  • index.d.ts byte identical

Verified on typescript 6.0.3

root type-check clean
examples tsc --noEmit clean
lint 0 errors, 23 pre-existing warnings
library tests 53 passed
demo tests 2 passed
build ESM + CJS + UMD, flat 117-line .d.ts
attw green on node10 / node16-CJS / node16-ESM / bundler
demo build passes

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated development tooling to support the latest TypeScript standards.
    • Modernized module generation and resolution settings for improved compatibility with current bundlers.
    • No user-facing features or behavior changes were introduced.

…tion

Supersedes #199, which cannot be merged on its own. The bump alone fails
type-check:

  tsconfig.json(16,25): error TS5107: Option 'moduleResolution=node10' is
  deprecated and will stop functioning in TypeScript 7.0.

Rather than silence it with ignoreDeprecations, which only defers the same
error to TypeScript 7, this moves both tsconfigs to module esnext with
moduleResolution bundler. That is the accurate description of this project
since #204: Vite does the bundling, and the published package resolves through
an exports map rather than node10 directory walking.

tsc no longer emits any JavaScript here, only declarations via
vite-plugin-dts, so the change cannot affect the shipped runtime. Confirmed by
building main and this branch and diffing lib/: no differences outside
sourcemaps, and index.d.ts is byte identical.

Verified on typescript 6.0.3: root and examples type-check, lint, 53 library
tests, 2 demo tests, the full ESM/CJS/UMD build, attw green on all four
resolution modes, and the demo build.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@codesandbox

codesandbox Bot commented Aug 8, 2026

Copy link
Copy Markdown

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@netlify

netlify Bot commented Aug 8, 2026

Copy link
Copy Markdown

Deploy Preview for react-xarrows ready!

Name Link
🔨 Latest commit 8a41acf
🔍 Latest deploy log https://app.netlify.com/projects/react-xarrows/deploys/6a778cdc2f60db0008a785af
😎 Deploy Preview https://deploy-preview-211--react-xarrows.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai

coderabbitai Bot commented Aug 8, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e328c85a-a0c9-41c2-893d-4081051a206b

📥 Commits

Reviewing files that changed from the base of the PR and between 166ab1e and 8a41acf.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (3)
  • examples/package.json
  • package.json
  • tsconfig.json

📝 Walkthrough

Walkthrough

The project updates TypeScript development dependencies to ^6.0.3. The compiler now emits ESNext modules and uses Bundler module resolution.

Changes

TypeScript configuration

Layer / File(s) Summary
TypeScript upgrade and module configuration
package.json, examples/package.json, tsconfig.json
The project and examples package update TypeScript from ^5.9.3 to ^6.0.3. The compiler changes from CommonJS and Node resolution to ESNext and Bundler resolution.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the TypeScript upgrade and module resolution changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch build/typescript-6

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

@Eliav2
Eliav2 merged commit 761c4ed into main Aug 8, 2026
6 checks passed
@Eliav2
Eliav2 deleted the build/typescript-6 branch August 8, 2026 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants