Bump strnum to 2.4.2 - #64
Merged
Merged
Conversation
A direct runtime dependency: the number coercion in DictionaryXmlFast is strnum's, declared beside fast-xml-parser because the fast reader calls it with the same options fxp would. 2.4.2 is in range of the existing "^2.4.1", so this is the lockfile alone — no package.json edit and no overrides entry, the same shape as the brace-expansion work. The resolved URL was rewritten back to registry.npmjs.org after the install, which the configured registry here does not do on its own; the integrity hash is content-based and unaffected. npm run check:leak clean.
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
1 participant
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.
Lockfile-only patch bump of a direct runtime dependency. 2.4.2 is in range of the existing
"^2.4.1", so there is nopackage.jsonedit and nooverridesentry — the same shape as the earlierbrace-expansionwork.resolvedrewritten back toregistry.npmjs.orgafter the install (the configured registry here writes an internal host);integrityis content-based and unaffected.npm run check:leakandnpm run typecheckclean.Note for the record:
npm teston this Mac fails 9 tests intest/mcosParser.test.tsandtest/publicTypeSurface.test.tsunder full-suite load — identically on cleanmainwith this change stashed, and both files pass in isolation with the change applied. Pre-existing local flake, not this bump.