oxc-project
oxc-resolver
Blog
Docs
Changelog
Blog
Docs
Changelog
Overview
Branches
Benchmarks
Runs
Performance History
Latest Results
chore: release v11.21.1
release-plz-2026-06-04T17-22-58Z
10 hours ago
test(bench-pm): add monorepo node_modules layouts (nested + cross-workspace) `packages/ui` depends on `react@17.0.2` while the app uses `react@18.3.1`, so the conflict un-hoists a nested `packages/ui/node_modules/react`; `packages/utils` links `@bench/ui` (workspace-to-workspace). Two `package_managers` workload requests resolve `react` from `packages/ui` (the nested 17) and `@bench/ui` from `packages/utils`; lockfiles regenerated for all combos.
perf/node-modules-anchor-fast-paths
10 hours ago
test: verify node_modules canonicalization across layouts (#1200) Adds a `node_modules` canonicalization test suite + committed symlink fixtures that assert the resolver's canonicalization equals `std::fs::canonicalize` across the layout families: - **`canonicalize_matches_os_for_all_node_modules`** — walks every path in each installed `fixtures/bench-pm/installs/<combo>/node_modules` tree (npm/pnpm/yarn/bun × flat/isolated/hoisted/pnp); skipped when the bench fixtures aren't installed. - **`symlinked_package_anchor_walks_suffix_symlinks`** — a symlinked workspace anchor with a symlink in the suffix below it. - **`real_package_anchor_walks_internal_symlinks`** — a real `node_modules/<pkg>` anchor that ships an internal directory/file symlink (`lib -> dist`, a re-export file). - **`nested_monorepo_canonicalize_matches_os`** — a monorepo version conflict where a workspace package nests its own dependency version via an isolated-store symlink (root resolves `dep@2`, `packages/ui` nests `dep@1`). These all pass on `main` — they pin canonicalization correctness independent of any resolver optimization, so they can land on their own (and guard #1189). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
main
10 hours ago
refactor(test): fold node_modules canonicalization tests into symlink.rs The canonicalization checks lived in a separate `node_modules_canonicalize.rs`; move them next to the existing symlink resolution tests so all canonicalization coverage is in one file.
perf/node-modules-anchor-fast-paths
12 hours ago
test: node_modules canonicalization across layouts Add canonicalization checks to `symlink.rs` (alongside the existing symlink resolution tests) with committed symlink fixtures, asserting the resolver's canonicalization equals `std::fs::canonicalize`: - `canonicalize_matches_os_for_all_node_modules` — walks every path in each installed `fixtures/bench-pm/installs/<combo>/node_modules` tree; skipped when the bench fixtures are not installed. - `symlinked_package_anchor_walks_suffix_symlinks` — a symlinked workspace anchor with a symlink in the suffix below it. - `real_package_anchor_walks_internal_symlinks` — a real anchor that ships an internal directory/file symlink. - `nested_monorepo_canonicalize_matches_os` — a monorepo version conflict where a workspace nests its own dependency version via an isolated-store symlink. These pass on main; they pin canonicalization correctness independent of any resolver optimization.
node-modules-canonicalize-tests
12 hours ago
test: verify node_modules canonicalization across layouts Add `node_modules_canonicalize.rs` and committed symlink fixtures asserting the resolver's canonicalization equals `std::fs::canonicalize`: - `canonicalize_matches_os_for_all_node_modules` walks every path in each installed `fixtures/bench-pm/installs/<combo>/node_modules` tree (skipped when the fixtures are not installed). - `symlinked_package_anchor_walks_suffix_symlinks` — a symlinked workspace anchor with a suffix symlink below it. - `real_package_anchor_walks_internal_symlinks` — a real anchor that ships an internal directory/file symlink. - `nested_monorepo_canonicalize_matches_os` — a monorepo version conflict where a workspace nests its own dependency version via an isolated-store symlink. These pass on main; they pin canonicalization correctness independent of any resolver optimization.
node-modules-canonicalize-tests
15 hours ago
test: add nested-monorepo canonicalization fixture A monorepo version conflict — root resolves `dep@2`, a workspace package nests its own `dep@1` via an isolated-store symlink. The test walks the fixture (incl. through symlinked directories) asserting the resolver's canonicalization equals `std::fs::canonicalize`, and checks each package's anchor resolves to its own store version.
perf/node-modules-anchor-fast-paths
15 hours ago
test(bench-pm): add monorepo node_modules layouts (nested + cross-workspace) The workspace packages had no dependencies, so every request resolved against the single root `node_modules` and the monorepo dimension was unexercised. Give them dependencies that create per-workspace `node_modules`: - `packages/ui` depends on `react@17.0.2` while the app uses `react@18.3.1`, so the conflict un-hoists a nested `packages/ui/node_modules/react` (flat) or `packages/ui/node_modules/react -> .pnpm/react@17.0.2/...` (isolated). - `packages/utils` depends on `@bench/ui` (`workspace:*`) — a workspace-to- workspace link; npm uses `*` via a config override. Two new `package_managers` workload requests resolve `react` from `packages/ui` (the nested 17) and `@bench/ui` from `packages/utils`. Lockfiles regenerated for all combos; `node_modules_canonicalize` now walks ~12.4k paths across the combos and still matches `std::fs::canonicalize`.
perf/node-modules-anchor-fast-paths
16 hours ago
Latest Branches
CodSpeed Performance Gauge
-2%
chore: release v11.21.1
#1201
10 hours ago
c48887f
release-plz-2026-06-04T17-22-58Z
CodSpeed Performance Gauge
-7%
perf: node_modules-anchor fast paths
#1189
10 hours ago
7cc5b97
perf/node-modules-anchor-fast-paths
CodSpeed Performance Gauge
+5%
test: verify node_modules canonicalization across layouts
#1200
16 hours ago
44566bd
node-modules-canonicalize-tests
© 2026 CodSpeed Technology
Home
Terms
Privacy
Docs