Repository navigation
chore(deps): apply the non-breaking npm audit fixes (40 -> 34 open advisories) - #24
Merged
Merged
Conversation
…visories) Runs `npm audit fix` with no --force, so only non-breaking resolutions moved. package-lock.json is the only file that changed; package.json ranges are untouched. Root npm audit: 40 -> 34 (1 critical, 19 high, 11 moderate, 3 low). Verified: lint pass, typecheck pass, test:data 9710 pass / 393 fail / 6 skipped of 10109 - identical to before the bump, so nothing regressed. The 393 failures are pre-existing and unrelated; see #23.
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Runs
npm audit fixwithout--force, so only non-breaking resolutions moved.package-lock.jsonis the only changed file — nopackage.jsonranges were touched.Result
GitHub reports 66 across the whole monorepo (including
scripts/and the sub-workspaces); the 40/34 figures are the root workspace.Verification
npm run lintnpm run typechecknpm run test:dataThe 393 failures are pre-existing and unrelated; see #23 for context.
What is deliberately NOT in this PR
Everything still open needs a major bump, which is a migration rather than a dependency bump:
maplibre-gl5.16 → 6.14 — the one remaining critical. XSS sanitizer bypass inDOM.sanitize()via Live NamedN...deck.gl8 → 9.1 — accounts for 9 of the 19 highs.@deck.gl/geo-layers,@deck.gl/mesh-layers,@loaders.gl/*,@luma.gl/gltfandtexture-compressorare all its components, so they move together.sharp,tailwindcss,image-size,micromatch,chokidar,globby,fast-glob,braces,markdownlint-cli2,@vercel/og,@xenova/transformersdeck.gl8→9 andmaplibre-gl5→6 both carry real API changes across the map layers. On a repo whose suite already has 393 pre-existing failures, driving those blind would make the failure count uninterpretable. Worth doing as its own piece of work with the suite as the safety net.