Walkthrough

Replaced Yarn commands and lockfile references with pnpm (and in many places added npm alternatives) across docs, CI/config, rake tasks, and scripts; removed one optional preinstall orchestration script. No public API or exported declarations changed.

Changes

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Files/items to pay extra attention to:
  • packages/react-on-rails/scripts/symlink-node-package — added per-example yalc link loop and switched link commands.
  • react_on_rails_pro/rakelib/dummy_apps.rake — task dependency change (yarn_install → pnpm_install) and command string updates.
  • Deletion: packages/react-on-rails-pro-node-renderer/script/preinstall.js — confirm no expectations or callers remain.
  • script/ci-changes-detector / SWITCHING_CI_CONFIGS.md — lockfile detection updates impacting CI flows.

Possibly related PRs

• Migrate from Yarn Classic to pnpm #2121 — Large yarn→pnpm migration touching docs, CI, and scripts; strong overlap.
• Reorganize PR testing docs into .claude/agents/ #2112 — Modifies PR Testing Agent docs that this PR also updates (yarn→pnpm edits).
• Update conductor-setup.sh to use pnpm #2212 — Similar pattern replacing Yarn with pnpm in repo tooling/setup scripts.

Suggested reviewers

• justin808
• AbanoubGhadban
• ihabadham

"I hopped through docs to change each yarn,
nibbling lockfiles till pnpm wears the crown,
Links relinked, preinstall trimmed neat,
Examples updated, scripts aligned to beat,
Now off I bound — the CI checks await!" 🐇✨

Pre-merge checks and finishing touches

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 help to get the list of available commands and usage tips.}

Code Review: Missed yarn→pnpm replacements

Summary

This PR completes the migration from Yarn to pnpm (PR #2121) by updating remaining yarn references in scripts and documentation. The changes are consistent, thorough, and improve the completeness of the pnpm migration.

✅ Positive Findings

1. Comprehensive Coverage

• 34 files updated across documentation, scripts, and analysis documents
• Systematic replacement of yarn → pnpm commands throughout the codebase
• Covers critical areas: CI scripts, developer guides, testing documentation, and configuration guides

2. Correct Command Mappings

• yarn install → pnpm install or pnpm install -r (for recursive workspace installs) ✓
• yarn run build → pnpm run build ✓
• yarn test → pnpm test ✓
• yarn.lock → pnpm-lock.yaml ✓
• yarn run yalc.publish → pnpm run yalc:publish ✓

3. Improved User Documentation
The update to docs/getting-started/installation-into-an-existing-rails-app.md is particularly good:

• Now shows all three package manager options (npm, yarn, pnpm)
• Clarifies the different --exact vs --save-exact flags
• More inclusive for users with different preferences

4. Script Consistency
Critical developer scripts properly updated:

• bin/ci-local - Local CI simulation
• bin/ci-rerun-failures - Failure reproduction
• bin/ci-switch-config - Environment switching
• conductor-setup.sh - Initial setup

5. Appropriate File Deletion
The removal of packages/react-on-rails-pro-node-renderer/script/preinstall.js is correct:

• File contained yarn-specific commands (yarn run link-source)
• No reference in package.json scripts
• Was likely a leftover from pre-pnpm workflow

🔍 Minor Observations

1. Lock File Patterns
In bin/ci-switch-config:

if [ -f pnpm-lock.yaml ]; then
  rm pnpm-lock.yaml
fi

This could be simplified to rm -f pnpm-lock.yaml (already using -rf for node_modules), but current approach is more explicit and equally correct.

2. Documentation Completeness
The changes correctly update:

• ✅ Command examples
• ✅ File path references
• ✅ Installation instructions
• ✅ CI/CD workflows
• ✅ Troubleshooting guides

🎯 Code Quality Assessment

• Consistency: ⭐⭐⭐⭐⭐ All replacements follow the same pattern
• Completeness: ⭐⭐⭐⭐⭐ Covers documentation, scripts, and analysis docs
• Correctness: ⭐⭐⭐⭐⭐ Command mappings are accurate
• Risk Level: 🟢 Low - These are documentation and script updates with no functional code changes

✅ Best Practices Followed

According to CLAUDE.md requirements:

• ✅ Documentation updates included
• ✅ No formatting changes needed (text-only changes)
• ✅ No trailing newline issues expected
• ✅ Changes align with monorepo migration strategy
• ✅ Follows project's "NEVER manually format" principle (text replacements only)

📋 Recommendations

Before Merge:

1. ✅ No RuboCop needed (no Ruby code changes)
2. ✅ No Prettier needed (markdown/shell script text changes)
3. ⚠️ Consider testing one of the updated scripts to verify commands work:

   # Quick validation
   ./bin/ci-switch-config status
   # or
   ./conductor-setup.sh --help

Post-Merge:

• Monitor CI to ensure all pnpm commands execute correctly
• Watch for any user-reported issues with installation instructions

🎉 Conclusion

LGTM! This is a high-quality cleanup PR that completes the pnpm migration. The changes are:

• Systematic and thorough
• Low-risk (documentation and scripts only)
• Well-aligned with the original migration (PR Migrate from Yarn Classic to pnpm #2121)
• Important for developer experience and onboarding

The PR successfully addresses the technical debt left from the initial migration and ensures consistency across the entire codebase.

Security & Performance

• ✅ No security concerns
• ✅ No performance implications
• ✅ No new dependencies introduced

Review completed using React on Rails project guidelines from CLAUDE.md

size-limit report 📦

Code Review - PR #2183: Missed yarn->pnpm replacements

✅ Overall Assessment

This PR successfully addresses the missed yarn→pnpm replacements from PR #2121. The changes are comprehensive, well-scoped, and all CI checks are passing. This is a documentation/configuration cleanup that improves consistency across the codebase.

🎯 Strengths

1. Comprehensive coverage: The PR updates 34 files across documentation, scripts, and analysis documents
2. Consistent patterns: All replacements follow the same pattern (yarn → pnpm) with appropriate flag updates
3. CI validation: All 31 CI checks passing, including linting, tests, and integration tests
4. No breaking changes: These are documentation/comment updates that don't affect runtime behavior
5. Good scope: Focuses purely on the yarn→pnpm migration without scope creep

📋 Changes Reviewed

Documentation Updates (✅ Good)

• Installation guides updated to mention npm/yarn/pnpm as alternatives
• Development guides now use pnpm consistently
• Quick start guide clarifies package manager flexibility
• Migration guide updated appropriately

Script Updates (✅ Good)

• bin/ci-local: Updated all yarn commands to pnpm
• bin/ci-rerun-failures: Updated yarn commands
• bin/ci-switch-config: Updated lock file references (yarn.lock → pnpm-lock.yaml)
• conductor-setup.sh: Updated setup instructions

Configuration Updates (✅ Good)

• Removed packages/react-on-rails-pro-node-renderer/script/preinstall.js (optional preinstall linking script - no longer needed)
• Updated Procfile references
• Updated lock file references in cleanup scripts

Analysis Documents (✅ Good)

• All .claude/docs/ analysis files updated consistently
• Historical references preserved but updated where commands are shown

🔍 Potential Issues Found

Minor: Remaining yarn references in docs/ directory

I found some remaining yarn references in the docs folder that may need attention:

# Check these files:
docs/JS_PRO_PACKAGE_SEPARATION_PLAN.md (multiple yarn references)
docs/api-reference/configuration.md:340 ("what yarn command is run")

Recommendation: These appear to be in historical/planning documents (JS_PRO_PACKAGE_SEPARATION_PLAN.md) which may be intentionally left as historical record. The one in configuration.md:340 should probably be updated to "what pnpm command is run" for consistency.

Minor: yarn binaries in dummy apps

The following yarn wrapper scripts remain (which is expected):

• react_on_rails_pro/spec/dummy/bin/yarn
• react_on_rails_pro/spec/execjs-compatible-dummy/bin/yarn

These are Rails bin stubs and may still be needed for compatibility. Worth verifying if these should stay or be removed/updated.

🧪 Testing Validation

CI Status: All checks passing ✅

• Lint JS and Ruby: SUCCESS
• Integration Tests: SUCCESS
• RSpec tests: SUCCESS
• Generator tests: SUCCESS
• Pro package tests: SUCCESS

No additional testing needed since:

1. These are documentation/comment changes
2. All automated tests pass
3. No runtime code affected

🎨 Code Quality

• Style consistency: ✅ All changes follow project conventions
• RuboCop compliance: ✅ No violations
• Formatting: ✅ Prettier/ESLint passing
• Breaking changes: ✅ None

📌 Recommendations

1. Before merging: Consider reviewing the remaining yarn references in:

   • docs/api-reference/configuration.md:340
   • Decide if docs/JS_PRO_PACKAGE_SEPARATION_PLAN.md should be updated (historical document)

2. Optional follow-up: Verify if the bin/yarn wrapper scripts in dummy apps are still needed

3. Documentation note: The PR description correctly notes this completes the yarn→pnpm migration started in Migrate from Yarn Classic to pnpm #2121

✅ Approval Recommendation

APPROVED ✅

This PR successfully completes the yarn→pnpm migration cleanup. The changes are thorough, consistent, and all tests pass. The minor issues noted above are optional and don't block merging.

Rationale:

• All CI checks passing
• Comprehensive and consistent changes
• No runtime impact
• Improves documentation consistency
• Follows project coding standards

Great work on the thorough cleanup! 🎉

Code Review - PR #2183: Missed yarn→pnpm replacements

Summary

Excellent cleanup work! This PR catches the remaining Yarn references that were missed in PR #2121's migration to pnpm. The changes are thorough and consistent across documentation, scripts, and configuration files.

✅ Strengths

1. Comprehensive Coverage: You've systematically updated:

   • Documentation files (.claude/, analysis/, docs/*)
   • Build scripts (bin/ci-local, bin/ci-rerun-failures, bin/ci-switch-config)
   • Developer setup scripts (conductor-setup.sh)
   • README files across dummy apps
   • Lock file references throughout

2. Consistency: All yarn → pnpm replacements follow the same pattern:

   • yarn install → pnpm install (or pnpm install -r for workspace recursive installs)
   • yarn run <script> → pnpm run <script>
   • yarn.lock → pnpm-lock.yaml

3. Removed Dead Code: Deleting packages/react-on-rails-pro-node-renderer/script/preinstall.js is correct—this file hardcoded yarn commands that are no longer needed.

4. Documentation Accuracy: Important clarifications like:

   • Updating WARP.md to say "ONLY use PNPM" instead of "Yarn Classic"
   • Adding multiple package manager options in user-facing docs (installation-into-an-existing-rails-app.md)

🔍 Observations & Suggestions

1. Minor Inconsistency in pnpm install Usage

Throughout the changes, I see both:

• pnpm install (simple install)
• pnpm install -r (recursive workspace install)

Question: Should some of the pnpm install commands in scripts like bin/ci-local and bin/ci-rerun-failures use pnpm install -r instead? For example:

# Line 167 in bin/ci-local
if ! (bundle install && pnpm install); then

Should this be pnpm install -r to ensure workspace dependencies are properly installed? This might not matter if pnpm handles it automatically, but worth clarifying for consistency.

2. Verification Needed: Does the Preinstall Deletion Break Anything?

The deleted packages/react-on-rails-pro-node-renderer/script/preinstall.js referenced a link-source script and used yalc.

Recommendation: Verify that:

• Any preinstall hooks in package.json that referenced this script are also removed
• The yalc workflow still works without this script
• No other scripts depend on the link-source functionality

Could you confirm this has been tested with the yalc workflow mentioned in CLAUDE.md's testing requirements?

3. SWITCHING_CI_CONFIGS.md Paths Need Monorepo Update

In SWITCHING_CI_CONFIGS.md, there's this section:

# Clean everything and try again
rm -rf node_modules pnpm-lock.yaml react_on_rails/spec/dummy/node_modules react_on_rails/spec/dummy/pnpm-lock.yaml
pnpm install -r
cd react_on_rails/spec/dummy && pnpm install

Issue: The paths react_on_rails/spec/dummy/ suggest this was written for a monorepo structure where react_on_rails is a subdirectory. But based on the git status showing we're in /home/runner/work/react_on_rails/react_on_rails, it seems we're already at the root.

Should these paths be:

rm -rf node_modules pnpm-lock.yaml spec/dummy/node_modules spec/dummy/pnpm-lock.yaml
pnpm install -r
cd spec/dummy && pnpm install

4. Analysis Files: Historical vs Current

Many files in .claude/docs/analysis/ contain historical references to yarn run yalc.publish that you've updated to yarn run yalc:publish.

Minor note: Some of these are analysis documents describing past incidents (like CI_FAILURES_2024-11-21.md). While updating them for consistency is fine, consider whether historical analysis files should preserve the exact commands as they were at the time of the incident vs. being updated to current conventions.

Not a blocker—just a philosophical question about whether historical docs should be updated or preserved as-is.

🔒 Security Considerations

✅ No security concerns. The changes are purely documentation and script updates with no code execution changes.

🧪 Test Coverage Recommendations

Per CLAUDE.md's critical requirements, before merging:

1. MANDATORY: Test clean install

   rm -rf node_modules
   pnpm install --frozen-lockfile

2. MANDATORY: Test build scripts

   pnpm run build
   pnpm run prepack
   pnpm run yalc:publish

3. Test the updated scripts

   # Test bin/ci-local with updated pnpm commands
   bin/ci-local --fast
   
   # Test bin/ci-switch-config if you have the environment
   bin/ci-switch-config status

4. Verify Pro package still works

   cd react_on_rails_pro
   pnpm install -r
   pnpm run nps test

🎯 Performance Considerations

✅ No performance impact. These are documentation and script updates only.

📝 Changelog

Per CLAUDE.md:

Do NOT add entries for: linting, formatting, refactoring, tests, or documentation fixes

✅ Correctly not updating CHANGELOG.md—this is purely documentation cleanup, not user-facing.

✅ Final Verdict

Approve with minor verification needed

This is excellent cleanup work that makes the codebase consistent with the pnpm migration. The changes are low-risk and improve developer experience by ensuring all documentation matches the actual tooling.

Before merging, please verify:

1. That the preinstall script deletion doesn't break the Pro package workflow
2. The path references in SWITCHING_CI_CONFIGS.md are correct for the current structure
3. Run the mandatory build script tests listed above

Great attention to detail in catching all these references! 🎉

Code Review - Missed yarn->pnpm replacements

Thank you for catching these missed replacements from PR #2121! I've reviewed the changes and found both strengths and areas for improvement.

✅ Strengths

1. Comprehensive coverage - You've updated numerous files across documentation, scripts, and configuration
2. Consistent pattern - The replacements follow a clear pattern (yarn → pnpm, yarn.lock → pnpm-lock.yaml)
3. Good catches - Important files like bin/ci-local, bin/ci-rerun-failures, and bin/ci-switch-config were updated
4. Deleted obsolete file - Removed packages/react-on-rails-pro-node-renderer/script/preinstall.js which was yarn-specific

⚠️ Issues Found

1. Incomplete yarn replacements in documentation

Several files still contain yarn commands that should be pnpm:

In .claude/docs/managing-file-paths.md:

• Lines 17-21: Still uses yarn run prepack and yarn build
• Lines 51-60: Still uses yarn build, yarn run prepack, and yarn install

In analysis files:

• Multiple analysis docs still reference yarn run prepack
• analysis/monorepo/MONOREPO_MIGRATION_CHECKLIST.md has mixed yarn/pnpm usage

The PR correctly changed yarn run yalc.publish → yarn run yalc:publish (fixing the dot-to-colon typo), but left the yarn part unchanged in many places.

2. Inconsistent command patterns

Some files now show:

# Inconsistent - still using yarn
yarn run prepack
yarn run yalc:publish

Should be:

pnpm run prepack
pnpm run yalc:publish

3. Missing updates in CLAUDE.md merge conflict section

CLAUDE.md line 387 correctly updated to pnpm run yalc:publish, but line 385 still says pnpm run prepack while the context in line 17-21 of managing-file-paths.md still uses yarn.

🔍 Suggested Fixes

Run this command to find all remaining yarn references in docs:

# Find remaining yarn commands in documentation
grep -rn "yarn run\|yarn install\|yarn build\|yarn test\|yarn add" \
  --include="*.md" \
  --exclude-dir=node_modules \
  --exclude-dir=.git \
  . | grep -v "yarn.lock" | grep -v "or yarn" | grep -v "pnpm/yarn"

Then update these files:

1. .claude/docs/managing-file-paths.md - Lines 17, 21, 51, 56-57, 60
2. .claude/docs/analysis/CLAUDE_MD_UPDATES.md - Multiple instances
3. .claude/docs/analysis/MIGRATION_QUICK_REFERENCE.md - Line 160
4. .claude/docs/analysis/claude-md-improvements.md - Lines 47, 49, 113
5. analysis/monorepo/MONOREPO_MIGRATION_CHECKLIST.md - Multiple instances

📋 Recommendations

1. Complete the migration - Update all remaining yarn references to pnpm
2. Keep flexible documentation - For user-facing docs (like installation-into-an-existing-rails-app.md), showing multiple package managers is good, but internal docs should be consistent
3. Run linting - Ensure bundle exec rubocop passes
4. No changelog needed - This is documentation-only, so skipping CHANGELOG is correct

🎯 Next Steps

1. Search for and replace remaining yarn commands in the files listed above
2. Run pnpm run format to ensure formatting is correct
3. Test that the updated commands work: pnpm run prepack, pnpm run yalc:publish

Overall, this is a valuable cleanup PR! Just needs a bit more thoroughness to catch all the stragglers.

Test Coverage: N/A (documentation only)
Security Concerns: None
Performance Impact: None
Breaking Changes: None

Code Review: Yarn to PNPM Migration Completeness

Thanks for catching these missed references! This PR is a valuable cleanup from PR #2121's yarn→pnpm migration. Here's my review:

✅ Strengths

1. Comprehensive coverage - The PR thoroughly addresses yarn references across:

   • Documentation (installation guides, READMEs)
   • Development scripts (bin/ci-local, bin/ci-rerun-failures, bin/ci-switch-config)
   • Configuration files (Procfiles, initializers)
   • Internal documentation (.claude/agents/, .claude/docs/)

2. Correct command replacements:

   • yarn install → pnpm install -r (with -r for recursive workspace installs)
   • yarn add → pnpm add
   • yarn upgrade → pnpm update
   • yarn.lock → pnpm-lock.yaml

3. Proper workspace syntax maintained - Kept workspace:* protocol references intact

4. Removed obsolete preinstall script - The deleted packages/react-on-rails-pro-node-renderer/script/preinstall.js was specific to yarn's optional dependency linking and is no longer needed with pnpm

📝 Observations & Suggestions

1. Lock file references in CI detector (script/ci-changes-detector):

   • Changed yarn.lock → pnpm-lock.yaml ✅
   • Good catch on this automation script

2. Documentation consistency:

   • docs/getting-started/installation-into-an-existing-rails-app.md now shows all three package managers (npm, yarn, pnpm) which is user-friendly ✅
   • Consider noting pnpm is the primary package manager for contributors in CONTRIBUTING.md if not already done

3. Typo in one location:

   • Line in .claude/agents/pr-testing-agent.md: yarn start format.listDifferent should be pnpm start format.listDifferent (looks like this was fixed ✅)

🔍 Testing Recommendations

Before merging, please verify:

1. Critical build scripts work:

   # Clean test
   rm -rf node_modules pnpm-lock.yaml
   pnpm install -r
   pnpm run build
   pnpm run yalc:publish

2. CI scripts execute without errors:

   bin/ci-switch-config status
   bin/ci-rerun-failures --help
   bin/ci-local --help

3. Documentation examples are accurate:

   • Spot-check a few README examples manually
   • Verify Procfile commands work

🎯 Quality Assessment

• Code Quality: ✅ Excellent - consistent replacements throughout
• Completeness: ✅ Very thorough search and replace
• Documentation: ✅ Well-maintained across all doc types
• Security: ✅ No concerns (removing unused preinstall script is good)
• Performance: ✅ No impact (documentation/script changes only)
• Test Coverage: ⚠️ No automated tests, but manual verification recommended (see above)

🚀 Recommendation

LGTM with manual testing. This is a solid cleanup PR. Once you've verified the critical build scripts work (especially after a clean install), this is ready to merge.

The removal of the preinstall script is correct - pnpm handles workspace dependencies natively and doesn't need the yarn-specific linking workaround.

Minor note: Consider running bundle exec rubocop to ensure any doc formatting is consistent (though these changes likely don't affect Ruby files).

Code Review - PR #2183: Missed yarn->pnpm replacements

Summary

This PR completes the yarn-to-pnpm migration by updating remaining references in scripts, documentation, and configuration files. All CI checks are passing ✅

✅ Positive Aspects

1. Thorough Migration Coverage

   • Correctly updates all documentation files (getting-started guides, README files, etc.)
   • Updates CI scripts (bin/ci-*, conductor-setup.sh)
   • Updates analysis/internal documentation in .claude/ directory
   • Updates Procfiles and task files

2. Proper Lockfile Handling

   • Correctly changes yarn.lock → pnpm-lock.yaml in scripts
   • Updates CI change detector to recognize pnpm-lock.yaml (critical for CI optimization)

3. Script Consistency

   • yarn install --frozen-lockfile → pnpm install --frozen-lockfile (correct)
   • yarn install --no-progress → pnpm install --no-frozen-lockfile (appropriate for non-CI contexts)
   • Package manager detection in conductor-setup.sh updated correctly

4. Documentation Improvements

   • Installation docs now mention all package managers (npm/yarn/pnpm) where appropriate
   • Uses correct flags: --save-exact (npm), --exact (yarn), --save-exact (pnpm)

5. Cleanup of Obsolete Code

   • Removes packages/react-on-rails-pro-node-renderer/script/preinstall.js
   • This script had yarn-specific commands and is no longer referenced in package.json
   • Good cleanup!

🔍 Areas for Consideration

Minor: Package Manager Flexibility Documentation

In docs/getting-started/installation-into-an-existing-rails-app.md:

# Use your preferred package manager
npm install react-on-rails --save-exact
# or: yarn add react-on-rails --exact
# or: pnpm add react-on-rails --save-exact

Suggestion: While this is good for compatibility, consider adding a note about which package manager the project itself uses (pnpm), so users understand the canonical approach. Something like:

# This project uses pnpm, but you can use your preferred package manager:
pnpm add react-on-rails --save-exact
# or: npm install react-on-rails --save-exact
# or: yarn add react-on-rails --exact

Verification Needed: yalc Command Consistency

Throughout the codebase, I notice:

• Some places use pnpm run yalc:publish (with colon)
• The actual package.json script is "yalc:publish": "yalc publish"

This appears consistent and correct. ✅

Verification: Procfile.dev rescript command

In react_on_rails/spec/dummy/Procfile.dev:

-rescript: yarn build:rescript:dev
+rescript: pnpm build:rescript:dev

Question: Does the package.json contain a build:rescript:dev script? If this uses pnpm run, it should be fine. Just want to confirm this was tested.

🔒 Security Considerations

✅ No security concerns identified

• The deleted preinstall.js was correctly removed (no longer needed)
• No credential exposure or security vulnerabilities introduced

🧪 Test Coverage

✅ All CI checks passing:

• Linting (JS and Ruby): SUCCESS
• Integration tests: SUCCESS
• Package tests: SUCCESS
• Generator tests: SUCCESS
• Pro package tests: SUCCESS

Recommendation: Given this changes build/CI scripts, it would be ideal to verify locally:

# Clean test as specified in CLAUDE.md
rm -rf node_modules pnpm-lock.yaml
pnpm install --frozen-lockfile
pnpm run build
pnpm run yalc:publish

# In conductor environment
./conductor-setup.sh

📊 Performance Considerations

✅ Positive impact:

• CI change detector now recognizes pnpm-lock.yaml, ensuring proper cache invalidation
• No performance regressions expected

🎯 Best Practices Adherence

Checking against CLAUDE.md requirements:

• ✅ Linting passing (no RuboCop violations)
• ✅ Files end with newlines
• ✅ Prettier/RuboCop handle formatting (no manual formatting)
• ✅ Changes are consistent with migration from yarn to pnpm (PR Migrate from Yarn Classic to pnpm #2121)
• ✅ Documentation updated appropriately
• ⚠️ Changelog: Not required per CLAUDE.md (not user-visible, internal tooling)

📝 Overall Assessment

Recommendation: APPROVE ✅

This PR successfully completes the yarn-to-pnpm migration started in PR #2121. The changes are:

1. Comprehensive - Covers scripts, docs, configs, and analysis files
2. Correct - Proper pnpm syntax and flag usage throughout
3. Safe - Removes obsolete code cleanly, no breaking changes
4. Well-tested - All CI checks passing

Minor suggestions for improvement:

1. Consider clarifying in user docs which package manager the project officially uses
2. Confirm the rescript Procfile command was tested locally

The PR is ready to merge as-is, with suggestions being optional enhancements.

Great work on being thorough with the migration! 🎉