Repository navigation
chore(deps): clean undici/npm overrides (drop dead nested rule) - #20
Merged
Merged
Conversation
Follow-up to #19: replace the obscure {npm:{.:...}} override with plain {npm:12.2.1} and drop the ineffective nested undici rule (the copy is bundled inside the npm tarball, inBundle, so no override shape can move it). Resolved tree identical: undici 8.12.2 top-level, npm 12.2.1, nested undici 6.29.0.
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
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.
Follow-up to #19. Same resolved tree (undici 8.12.2, npm 12.2.1, nested undici 6.29.0), readable config: the nested npm:{undici} rule cannot work because that copy is bundled inside the npm tarball (inBundle, proven on both repos), and the . key is obscure. Remaining nested < 6.29.1 alerts stay open, blocked on an upstream npm release bundling undici >= 6.29.1 (newest npm 12.2.1 still bundles 6.29.0).