chore: update package-lock for latest npm 11

[jonchurch]

This should stabilize the lockfile, Im getting a lockfile diff on npm i w/ npm 11.12.1, which we have pinned in the package.json now.

I think the diff here is bc npm 11 had some bugs or something w/ peer dep bookkeeping, so the lockfille was generated in an earlier version of 11, and since like 11.10 something whatever bugs existed were fixed.

This diff is just from running npm i here with

node -v
# 24.15.0
npm -v
# 11.12.1

[netlify]

✅ Deploy Preview for expressjscom-preview ready!

Name	Link
🔨 Latest commit	53dead3
🔍 Latest deploy log	https://app.netlify.com/projects/expressjscom-preview/deploys/6a0bb72a92dfd600086faae4
😎 Deploy Preview	https://deploy-preview-2326--expressjscom-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 99 (🟢 up 2 from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[bjohansebas]

I wish npm had an option to freeze the lockfile instead of having to use npm ci. The same thing happened to me in webpack, so I’m not sure this will help much because it seems like it will always get regenerated