rstackjs/rspack-resolver - CodSpeed

rspack-resolver

Blog Docs Changelog

Performance History

Latest Results

chore(deps): update napi

renovate/napi

1 day ago

chore(deps): update crate-ci/typos action to v1.46.1

renovate/typos

1 day ago

chore(deps): update napi

renovate/napi

3 days ago

fix(tsconfig): detect cycles when walking project references A pair of project references that point at each other (a → b → a) previously caused infinite recursion when `references: "auto"` recursively loaded the graph, blowing the test thread's stack. Add a `visited` set threaded through `load_references`. Each tsconfig inserts its own path before walking its references. When a candidate reference's loaded path is already in the chain, the cycle edge is cut: the reference is still attached so its own `paths` are honored, but its nested references are not walked. Includes a `references-cycle` fixture (a ↔ b) and a `cyclic_references` test that asserts resolution succeeds from both sides without stack overflow. Direct self-reference (A → A) detection via the existing equality check inside the cache callback is preserved.

feat/tsconfig-transitive-references

3 days ago

test(tsconfig): add focused test for references with extends Add a dedicated test (`references_with_extends`) and fixture (`references-extends/`) that exercises the fix from the previous commit in isolation: a single-level reference whose `baseUrl`/`paths` are inherited via `extends "../tsconfig.base.json"`. Without `merge_tsconfig_extends` being applied to the reference, the test fails with `NotFound` — confirming the test would have caught the latent extends-on-reference bug. Also revert the `references-transitive` fixture so it focuses purely on multi-level walking; the extends-merging behavior is now covered by the new fixture and test.

feat/tsconfig-transitive-references

3 days ago

fix(tsconfig): apply `extends` to project references before recursing When a project reference uses `extends` to inherit its `baseUrl`/`paths` from a shared base config, those fields must be merged before the reference is consulted for resolution. The previous flow loaded each reference through `cache.tsconfig` and only ran the extends-merging logic on the entry tsconfig, so a transitively-referenced project whose aliases live in an extended base file would resolve as if it had no aliases at all. This was a pre-existing latent bug at depth 1 — direct references with `extends` did not inherit their aliases either — that the new transitive-references support made easier to hit. Changes: - Extract `merge_tsconfig_extends` from `load_tsconfig` and call it from `load_references`' inner callback after the self-reference check, before recursing into nested references. - Update the `references-transitive` fixture: `project_c` now reads its `paths` from a sibling `tsconfig.base.json` via `extends`. The existing `transitive_references` test fails before this fix (NotFound) and passes after. Detected via Codex review of #213.

feat/tsconfig-transitive-references

3 days ago

chore(deps): update crate-ci/typos action to v1.46.1

renovate/typos

3 days ago

test: sync enhanced-resolve#579 tsconfig paths fall-through (#212)

main

3 days ago

Latest Branches

0%

chore(deps): update napi#214

1 day ago

f4b0280

renovate/napi

0%

chore(deps): update crate-ci/typos action to v1.46.1#208

1 day ago

2f9b96d

renovate/typos

+1%

fix(tsconfig): support transitive project references for paths resolution#213

3 days ago

23b8954

feat/tsconfig-transitive-references

© 2026 CodSpeed Technology

Home Terms Privacy Docs