Repository navigation
docs: clarify installation, release scope and workload selection - #32
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. 🧰 Additional context used📚 Code guidelines (2)No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (9)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe documentation now distinguishes ChangesDocumentation guidance
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Other Merge Risk: ⚪ Minimal · up to The documentation clarifies installation, release scope, and workload selection without changing runtime behavior. No actionable merge-blocking risk is established; merge after normal checks. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Problem and native value
The homepage incorrectly said the package rename was unpublished, while Quick Start referred to npm 0.1.0 without providing an install-to-first-run path. Readers could also mistake main's compatibility fixes and benchmark results for the published release.
Clarify the release/main boundary throughout onboarding, add a runnable scan example, supported binary platforms, migration steps and troubleshooting, and link workload choices to both wins and losses. Add grouped links to all 26 benchmark tables for easier navigation on narrow screens and use the official site as the metadata base.
Compatibility and tests
Documentation only; public APIs, native routing and benchmark data are unchanged. Existing conformance and performance evidence remains applicable. No new filesystem tests or benchmark runs are warranted.
Performance evidence
No runtime change. Recommendations link to the existing full tables and preserve platform, workload and release limitations.
Documentation and validation
pnpm doc:build, formatting checks,pnpm lintandgit diff --check.@vooya/fs@0.1.0into a fresh temporary project and successfully ran the exact scan example against a TypeScript fixture.fs-v0.1.0source tag.Summary by CodeRabbit
@vooya/fs@0.1.0package from the unreleasedmainversion, with revised installation, migration, and first-scan guidance.