@rolldown/debug
1.3.3 · 18 Nov 2026MIT312.2k / weekRepositoryHomepagenpmAtom feed
Upgrading @rolldown/debug From 1.1.1 to 1.1.2
1 release in betweenevery note read
Reading releases, release notes and advisories…
Release by release
- New
Add option named for invalid return type errors for more places
- New
Add option names for invalid return type errors
- New
transform: Infer decorator strictNullChecks from tsconfig
- New
tracing: Gate chrome-json trace layer behind
chrome-tracingfeature
- New
2 other lines we could not sort, mostly version bumps
- 1.1.2
Honor explicit non-TS extensions in
include(oxc-project/oxc-resolver#1213).compilerOptions.pathsnow resolve for importers whose extension is explicitly listed in a tsconfig'sinclude(e.g.src/**/*.vue,src/**/*.svelte). Previously oxc-resolver filtered importers by extension before evaluating theincludeglobs, so a.vue/.sveltefile listed inincludenever matched its project and itspathswere skipped. This unblocks the default create-vite Vue + TS layout (a solution-style root plus a referencedtsconfig.app.jsonthat declarespathsandinclude: ["src/**/*.ts", "src/**/*.vue"]). Matches vue-tsc and svelte-check, which register these extensions via TypeScript'sextraFileExtensions. - 1.1.2
No fallback to the outermost tsconfig in auto-discovery (oxc-project/oxc-resolver#1220). Auto-discovery no longer attaches the topmost ancestor
tsconfig.jsonto a file that no project actually owns (viafiles/include/ project references). Previously such a file inherited the outermost ancestor'spaths/baseUrl, leaking aliases into files that project does not own. oxc-resolver now returns no config in that case, matching tsserver / typescript-go, which route such files to an inferred project with no aliases.
60 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.