This is a NextJS project for Drone4Build homepage.
use nvm
yarn installand run the project with:
yarn devKeeping packages current matters: security patches, bug fixes, and Next.js/React improvements ship in newer versions, and letting dependencies drift too far behind makes future upgrades riskier and harder to do incrementally.
Process:
-
Check what's outdated:
yarn outdated
-
Bump patch/minor versions within existing semver ranges (low risk):
yarn upgrade
-
Bump major versions one package at a time, not in bulk. After each one, verify before moving to the next:
yarn add <package>@<version> yarn tsc --noEmit yarn build
yarn buildalone does not catch type errors (Next.js skips type validation during build), sotsc --noEmitis required separately. -
Manually test the app in the browser (
yarn devor a production build) — type checking and build success verify code compiles, not that features still behave correctly. -
Commit each verified upgrade (or a small verified batch) separately, keeping
yarn.lockin sync withpackage.json, so a regression can be bisected to a single dependency bump.
If a major bump breaks the build, lint, or types, revert just that package and leave it for a later, dedicated upgrade rather than blocking the rest.
Hosted on Vercel, connected to this GitHub repository. Pushes to main deploy to production; other branches/PRs get preview deployments automatically. Environment variables (see .env.sample) are set in the Vercel project settings.