fix: avoid Windows path alias mismatch in symlink map - #2411
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe symlink helper now runs ChangesFixture symlink discovery
Estimated code review effort: 2 (Simple) | ~5 minutes Merge Risk: ⚪ Minimal · up to This localized change adjusts symlink-map path handling for Windows without introducing a known correctness or production risk; no actionable merge-blocking risk remains after normal checks and review. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
Run
git ls-filesfrom the fixture root so Git returns paths relative to the same directory used by Node.Why
The regression test added in #2410 fails on the GitHub Windows runner. Git reports the temporary profile through its short
RUNNER~1alias, while Node keeps therunneradminpath. Callingpath.relative()across those two forms produces a pathspec outside the repository, whichgit ls-filesrejects.Running the command from the fixture root avoids that path conversion and keeps the map entries relative to
rooton every platform.Validation
server-only.test-make-symlinks-map.js: 1 passednps build.indexjson: preserved the symlink map and removed its fetch-index entrygit diff --checkpassedkarma-matrixhead.Follow-up to #2410. This fixes the Windows failure currently reported on #2383.
Summary by CodeRabbit