fix: read module replacements from mappings - #253
Merged
Conversation
gameroman
approved these changes
Aug 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
Fixes #252
📚 Description
npm run whichcrashes because it tries to readmoduleReplacements, but that field does not exist inmodule-replacementsv3.This change reads the native and micro-utility mappings with
Object.values()instead.I did not use
allbecause it also includes preferred replacements. In #84, the script was intentionally limited to native and micro-utility replacements so the progress number stays correct.The README still recommends
npm run whichto contributors looking for a codemod to work on.