Skip to content

chore(deps): refresh lockfile to latest in-range versions#118

Merged
luflow merged 1 commit into
mainfrom
deps/npm-update-2026-07
Jul 26, 2026
Merged

chore(deps): refresh lockfile to latest in-range versions#118
luflow merged 1 commit into
mainfrom
deps/npm-update-2026-07

Conversation

@luflow

@luflow luflow commented Jul 26, 2026

Copy link
Copy Markdown
Owner

npm update + npm audit fix — 59 packages, all patch/minor within the ranges already declared in package.json. No package.json change, no overrides, diff is package-lock.json only.

Why

Clears the second high-severity advisory in the tree:

  • fast-uri 3.1.3 → 3.1.4GHSA-v2hh-gcrm-f6hx, host confusion via literal backslash authority delimiter. Dev-only, via stylelint and vite-plugin-dts@microsoft/api-extractor.

8 of the 59 are production deps, all uneventful: marked 18.0.6→18.0.7, postcss 8.5.19→8.5.23, p-queue 9.3.1→9.3.3, sax 1.6.0→1.6.1, @vue/devtools-* 8.1.5→8.2.1, @vue-macros/common 3.1.3→3.1.4. The rest is tooling (eslint 10.7.0→10.8.0, playwright 1.61.1→1.62.0, typescript-eslint 8.64→8.65, sass, stylelint, …).

The lockfile's version field also drifted (1.40.0 vs. 1.41.2 in package.json); this syncs it.

Relationship to #117

This includes the brace-expansion 5.0.7 → 5.0.8 bump from #117, since npm update picks it up as well. Either merge #117 first and I'll rebase this, or merge this one and close #117 as covered — whichever you prefer. Both target main directly.

What remains, and why it can't be fixed here

Advisory Severity Status
brace-expansion@2.1.2 via minimatch@9 high npm audit: no fix available. 2.1.2 is the latest maintenance-v2 release, no 2.x backport upstream. Overriding to 5.x breaks minimatch@9, which calls the default export where v5 exports a { expand, … } object.
elliptic via vite-plugin-node-polyfills low No fix available upstream. Dev-only.

Reported total drops from 17 to 16, but the meaningful count is 3 distinct advisories → 2, neither actionable.

Verification

  • npm ci from a clean checkout of main, then npm update — result is byte-identical on repeat, so the lockfile is reproducible
  • npm run build passes
  • npm run lint unchanged from the main baseline (7 errors / 17 warnings, all pre-existing — vue/max-attributes-per-line and @stylistic/implicit-arrow-linebreak, untouched by this PR)
  • Diff is package-lock.json only, no build artefacts

Runs `npm update` plus `npm audit fix`, which touches 59 packages, all
patch/minor within the ranges already declared in package.json. No
package.json change and no overrides.

This clears the second high-severity advisory, fast-uri 3.1.3 -> 3.1.4
(GHSA-v2hh-gcrm-f6hx, dev-only via stylelint and vite-plugin-dts), and
includes the brace-expansion 5.0.7 -> 5.0.8 bump of CVE-2026-14257.

The two advisories that remain have no fix available upstream:
brace-expansion 2.1.2 via minimatch@9 (no 2.x backport) and elliptic via
vite-plugin-node-polyfills (dev-only).

Also syncs the lockfile's version field to 1.41.2, which had drifted
from package.json.
@luflow
luflow merged commit 60b29db into main Jul 26, 2026
2 checks passed
@luflow
luflow deleted the deps/npm-update-2026-07 branch July 26, 2026 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant