Repository navigation
deps: refresh lockfile within existing ranges - #10
Conversation
Re-resolve pnpm-lock.yaml with pnpm 10 without changing any manifest specifier. Top-level movements inside the existing ranges: - postcss 8.5.8 -> 8.5.31 (patched for the source-map/path-traversal advisories, patched >=8.5.18) - @tailwindcss/postcss 4.2.1 -> 4.3.3, tailwindcss 4.2.1 -> 4.3.3 - eslint 9.39.4 -> 9.39.5, eslint-config-next 16.1.6 -> 16.4.2 - react-hook-form 7.71.2 -> 7.90.0, tailwind-merge 3.5.0 -> 3.7.0 - @types/node 22.19.13 -> 22.20.5, autoprefixer 10.4.27 -> 10.6.1 Transitive resolutions pick up @babel/core 7.29.7 (patched >=7.29.6), floating-ui, js-yaml, flatted and nanoid fixes; pnpm audit drops from 83 reported vulnerabilities to 43.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Independent CI for head The |
There was a problem hiding this comment.
Reviewed head 61b3c7e against main 70f4921 in isolated worktrees (Node 22.22.3 / pnpm 10.34.9).
- Frozen-lockfile install, production static export, and explicit
tsc --noEmit: pass. The repository's build intentionally skips type checking, so types were checked separately. - Chromium full-page screenshot comparison: 16/16 with no perceptible visual difference (pixelmatch threshold 0.1), with identical section/heading geometry, text, links and SVG counts. Matrix: 1440, 768, 390 and 320px widths × English/Chinese × light/dark CSS class.
- Live language toggle (mouse and keyboard), hero CTA, desktop/tablet section links, sticky navigation and logo return-to-top: pass. No broken fragment targets or new horizontal overflow; no hydration/runtime errors or failed page assets.
- Test caveat: the Vercel-only
/_vercel/insights/script.jsreturns 404 on the static localhost baseline; it was stubbed identically for both versions, not changed in source. - Scope is lockfile-only. Correction to the PR description: baseline
pnpm lintpasses, while this head introduces 3 lint failures via the newereslint-config-nextrule set (react-hooks/set-state-in-effectin carousel and the two mobile hooks). Existing source patterns, but newly failing lint, not “identical on main.” This is non-blocking under the requested UI/UX merge criterion; no page or lint suppression changes made.
The existing GitHub dependency build check is green. Approved for merge under the requested UI/UX criterion.
Raw RGBA comparison note: a few rounded-border anti-aliasing channels in the language button differ by at most 1/255; layout is identical and significant-difference pixels are zero. This is visual equivalence, not a claim of byte-identical PNGs.
Refresh
pnpm-lock.yamlwithin existing ranges (no manifest change)Lockfile-only refresh: every
package.jsonspecifier is unchanged, so pinned (next,react,@radix-ui/*, …) and caret ranges keep their existing style and floors.Top-level resolutions inside the current ranges
postcss@tailwindcss/postcss/tailwindcsseslinteslint-config-nextreact-hook-formtailwind-mergeautoprefixer@types/nodeTransitive movements include
@babel/core7.29.0 → 7.29.7 (patched ≥ 7.29.6),@floating-ui/*,js-yaml,flatted,nanoidandbrace-expansion.Effect on advisories
pnpm auditonmain(70f4921): 83 reported vulnerabilities (2 critical, 45 high).On this branch: 43 reported vulnerabilities (2 critical, 19 high). The remaining criticals and most highs are
next@16.1.6itself — handled separately in #9 (that PR is not required for this one to be valid, and merging both in any order just needs a lockfile re-resolve).eslint@9.39.5prints an upstream deprecation warning ("no longer supported"); the next supported line iseslint@10, a major that is out of scope here.Validation (local, pnpm 10.34.7 / Node 20.20.2)
pnpm install --frozen-lockfile— passpnpm build— pass (next build,✓ Compiled successfully)pnpm lint— 3 pre-existingreact-hooks/set-state-in-effecterrors, same asmain; not a regression and not part ofdependency-checks.ymlIndependent CI (
Dependency checks) is dispatched against this branch head and its result is linked in the follow-up comment.