chore(deps): fix npm audit vulnerabilities and loosen three peer range (v1.6.2)#19
Merged
Merged
Conversation
- npm audit fix: protobufjs 8.5.0->8.6.5, esbuild 0.28.0->0.28.1 (0 vulns) - widen `three` peerDependency to `>=0.173.0` so consumers on newer three (0.174+) no longer hit peer conflicts (caret locks 0.x minors) - bump version to 1.6.2
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.
Summary
npm audit fix: bumpprotobufjs8.5.0 -> 8.6.5 (moderate) andesbuild0.28.0 -> 0.28.1 (low);npm auditnow reports 0 vulnerabilities. Lockfile-only, within existing semver ranges.threepeerDependency from^0.173.0to>=0.173.0. Sincethreeis a0.xpackage, caret only allows>=0.173.0 <0.174.0, causing peer-conflict warnings for consumers on newer three (0.174+, now 0.18x).@react-three/fiber/drei/reactkeep caret.1.6.2.Verified:
libExternal()invite.lib.config.tsexternalizes only the react/three ecosystem, which stays consistent with the declaredpeerDependencies(no silent required installs).Test plan
npm audit-> 0 vulnerabilitiesnpm run typechecknpm run build:lib