Improve efficiency of yarn-install's registry overrride step #373
+27,920
−23
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.
Description
Working with yarn-install I have noticed it's registry override step is quite complex and is not as fast as it could be, so I just asked an LLM to rewrite script to do the same thing but in one pass over yarn.lock and got a working solution that's also kind of more straightforward
Here's performance comparison of existing and new implementation on yarn.lock taken from toptal/client-portal:
How to test
Development checks
PR commands
List of available commands:
@toptal-anvil ping reviewers
- Ping teams for review