Update dependencies and refresh Next.js quickstart lockfile#200
Update dependencies and refresh Next.js quickstart lockfile#200dex-the-ai wants to merge 2 commits into
Conversation
|
Owner ping for this maintenance PR: @ejscribner Requesting review from the manifest-listed owner(s) where GitHub does not already show a pending review request. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Code Review
This pull request updates several dependencies and devDependencies in package.json and package-lock.json, including upgrading axios, next, qs, eslint, eslint-config-next, and postcss to their latest versions. I have no feedback to provide as there are no review comments and the changes are standard dependency updates.
|
I pushed a workflow-only follow-up. The previous red |
Summary
axios,next,qs,eslint,eslint-config-next, andpostcsspackage-lock.jsonon Node 24 with the corresponding safe transitive patchesVerification
npm run checknpm run init-db:defaultnpm testnpm run init-db:local./node_modules/.bin/env-cmd -f tutorial-maintenance/runs/nextjs-quickstart/2026-05-26T19-40-00Z/build.env npm run buildnpm run dev -- --hostname 127.0.0.1 --port 3000and exercised create/update/delete flows through the live API surfaceEvidence
format + lint passed on the updated dependency set
Jest passed all 4 suites / 6 tests against the local Couchbase-backed test setup
the temp-bucket build gate completed successfully, including sample-data load and index creation
the live walkthrough listed seeded profiles, created a profile, updated it, deleted it, and verified removal afterward
Test output
Walkthrough excerpt
tutorial-maintenance/runs/nextjs-quickstart/2026-05-26T19-40-00Z/verification.mdNotes
npm audit --audit-level=moderatestill points at breaking-major follow-ups (next-test-api-route-handler@5,uuid@14) plus the advisory path reported through Next’s bundledpostcss, so I kept this PR to the smallest verified safe updates.npm run builddirectly against the long-lived localuser_profilebucket still trips over the existing non-idempotent sample-data load step once those docs are already present; the clean-bucket build check above passed successfully.Media evidence
user_profilebucket.Notes
tutorial-maintenance/runs/nextjs-quickstart/2026-05-26T19-40-00Z/homepage.pngNotes
tutorial-maintenance/runs/nextjs-quickstart/2026-05-26T19-40-00Z/homepage.webm