Skip to content

fix(examples): apply front-end security updates, keep Tailwind 3 - #927

Open
bnusunny wants to merge 1 commit into
mainfrom
fix/frontend-security-sweep
Open

bnusunny wants to merge 1 commit into
mainfrom
fix/frontend-security-sweep

Conversation

@bnusunny

@bnusunny bnusunny commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Applies the security updates from 15 stale or conflicting Dependabot PRs by hand, for the remix, remix-zip, nextjs, nextjs-response-streaming and nextjs-zip examples. Dependabot's own lockfile regeneration moved tailwindcss to 4.x, which broke the builds (#881, #884, #902: "trying to use tailwindcss directly as a PostCSS plugin"); every lockfile here keeps its Tailwind major.

Rebased onto main after #901 and #903 merged. Those two lockfiles were regenerated with npm on top of main, not merged by hand.

Example Change
remix, remix-zip npm audit fix (body-parser, express, proxy-addr, compression, morgan, qs, undici, …), vite ^6.4.6
nextjs next 15.5.29, postcss ^8.5.32
nextjs-response-streaming postcss 8.5.32, yaml/minimatch/picomatch (on top of next 15.5.28 from #901)
nextjs-zip flatted (on top of next 15.5.28 / sharp 0.35.5 from #903)

Testing

npm ci && npm run build passes for remix, remix-zip and nextjs (the first two are in the CI matrix). nextjs-response-streaming and nextjs-zip fail to build identically on main (Next 15 async params type error; Tailwind 4 PostCSS plugin). They are not in the CI matrix; fixing them is a separate example change.

npm audit --omit=dev (vulnerable packages, main → this PR): remix 14 → 7, remix-zip 14 → 7, nextjs 4 → 2, nextjs-zip 2 → 2 (dev-only fix). No critical left in any of the five. nextjs-response-streaming goes 6 → 10 packages, but its distinct advisories drop 12 → 6. Once the fixable picomatch advisories are gone, npm blames the one with no 2.x fix (GHSA-fc5q-39xc-vjpf) on tailwindcss 3 and its chokidar/fast-glob chain. The remaining postcss advisories come from next's bundled postcss 8.4.31.

Replaces #902, #666, #801, #884, #776, #699, #741, #804, #881, #680, #818, #665, #682, #813, #670.

@bnusunny
bnusunny requested a review from a team as a code owner November 13, 2026 19:51
Hand-applied security updates for the remix, remix-zip, nextjs,
nextjs-response-streaming and nextjs-zip examples, replacing 15 stale
or conflicting Dependabot PRs. Dependabot's own lockfile regeneration
moved tailwindcss to 4.x, which removed the PostCSS plugin these
examples use; every lockfile here keeps the Tailwind major it had.

- remix, remix-zip: npm audit fix (no --force): body-parser 1.20.9,
  express 4.22.3, proxy-addr 2.0.8, compression 1.8.2, morgan 1.12.1,
  qs 6.16.2, undici, flatted, source-map-js, brace-expansion; vite
  ^5.1.0 -> ^6.4.6 (in @remix-run/dev 2.17 peer range; the open GitHub
  vite advisories are patched in 6.4.4). Both apps build on vite 6.
- nextjs: next 15.5.24 -> 15.5.29, postcss ^8.5.32, plus audit fix.
- nextjs-response-streaming: postcss 8.5.10 -> 8.5.32, audit fix
  (yaml, minimatch, picomatch). Rebased on #901 (next 15.5.28).
- nextjs-zip: flatted 3.4.4 only. Rebased on #903 (next 15.5.28,
  sharp 0.35.5).

npm audit --omit=dev critical/high/total, main -> this change:
remix 1/8/14 -> 0/5/7, remix-zip 1/8/14 -> 0/5/7 (vite is a dev
dependency, so --omit=dev does not count it),
nextjs 1/3/4 -> 0/1/2, nextjs-zip 0/1/2 -> 0/1/2 (dev-only fix).
nextjs-response-streaming reports 0/3/6 -> 0/8/10, but distinct
advisories drop 12 -> 6: once the fixable picomatch advisories are
gone, npm attributes the unfixed one (GHSA-fc5q-39xc-vjpf, no 2.x
release) to tailwindcss 3 and its chokidar/fast-glob chain. The
remaining postcss advisories are next's bundled postcss 8.4.31.
@bnusunny
bnusunny force-pushed the fix/frontend-security-sweep branch from 94217c9 to 4798473 Compare November 17, 2026 22:35
@bnusunny
bnusunny requested a review from vicheey November 20, 2026 15:29

This branch has not been deployed

No deployments
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