Add engine restrictions to migration package#3066
Conversation
WalkthroughAdded a Node.js version constraint to the migration package's package.json file specifying support for versions ^20.19.0, ^22.12.0, or ^24.0.0. This single configuration field addition restricts which Node.js runtime versions can execute the migration package. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used🧠 Learnings (3)📓 Common learnings📚 Learning: 2025-09-29T06:06:58.605ZApplied to files:
📚 Learning: 2025-09-29T06:00:16.488ZApplied to files:
🔇 Additional comments (1)
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 |
- This reverts #2974 (Not going to go that direction) - Instead, sets the module `preserve`, target `esnext` and `bundler` resolutions, to rely on `tsdown` builds - All targets are configured to the lowest supported Node version by #3066 and #2912 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Refactor** * Standardized module import paths across the codebase to improve compatibility and consistency. * Updated TypeScript configuration for enhanced module resolution handling. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Need this for consistency and proper
tsdownbuildSummary by CodeRabbit