fix(blog): correct codemod references in v22-to-v24 migration guide - #9095
fix(blog): correct codemod references in v22-to-v24 migration guide#9095blue2cat wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull request overview
Updates the Node.js v22→v24 migration guide to ensure codemod references align with the published recipe/registry names and improves copy clarity so users can successfully locate and run the intended codemods.
Changes:
- Corrects codemod naming to match published recipes (e.g.,
http2-priority-signaling,fs-truncate-fd-deprecation). - Adds/aligns source code and Codemod Registry references for consistency.
- Fixes minor wording/typos that could confuse readers when following the guide.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
Thanks for catching that seem copy pasta or idk form my part |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9095 +/- ##
==========================================
+ Coverage 75.13% 75.14% +0.01%
==========================================
Files 102 102
Lines 9114 9114
Branches 376 376
==========================================
+ Hits 6848 6849 +1
+ Misses 2262 2261 -1
Partials 4 4 ☔ View full report in Codecov by Harness. |
📦 Build Size ComparisonSummary
|
Description
After #9082 was merged, I noted several other issues in this post.
http2-priority-removaltohttp2-priority-signalingto match the published codemod namefs-truncate-to-ftruncateheading tofs-truncate-fd-deprecation. This makes it consistent with the codemod name.Validation
Related Issues
Check List
pnpm formatto ensure the code follows the style guide.pnpm testto check if all tests are passing.pnpm buildto check if the website builds without errors.