Next.js/NestJS App Feature Upgrade
Budget: $250 – $750 USD
The application is already live, built with Next.js on the client side, NestJS powering the API layer, and a MySQL database underneath. What I need now is a focused upgrade that adds new business-oriented features without disturbing the current user base or data integrity.
Key context
• Current stack: Next.js, NestJS, MySQL, Git for version control
• Goal of this phase: extend functionality rather than rewrite anything
• Performance and UI are acceptable for now; the emphasis is strictly on adding the next wave of business features
Scope of work
1. Analyse the existing codebase, paying particular attention to service boundaries in the NestJS layer and the way the Next.js pages consume data.
2. Design and implement the agreed-upon business features—including migrations, new modules, routes, controllers, and any additional React components—while following established project conventions.
3. Update unit/integration tests where new logic is introduced.
4. Provide a concise hand-over note so the internal team can maintain what you add.
Acceptance criteria
• New endpoints and UI screens compile and pass existing CI checks.
• MySQL migrations execute cleanly on staging and production.
• No regression in current features, confirmed via the automated test suite.
Everything lives in a private Git repo; you’ll push to feature branches and open merge requests for review. Once merged and deployed to staging, we’ll verify together before promotion to production.
Key context
• Current stack: Next.js, NestJS, MySQL, Git for version control
• Goal of this phase: extend functionality rather than rewrite anything
• Performance and UI are acceptable for now; the emphasis is strictly on adding the next wave of business features
Scope of work
1. Analyse the existing codebase, paying particular attention to service boundaries in the NestJS layer and the way the Next.js pages consume data.
2. Design and implement the agreed-upon business features—including migrations, new modules, routes, controllers, and any additional React components—while following established project conventions.
3. Update unit/integration tests where new logic is introduced.
4. Provide a concise hand-over note so the internal team can maintain what you add.
Acceptance criteria
• New endpoints and UI screens compile and pass existing CI checks.
• MySQL migrations execute cleanly on staging and production.
• No regression in current features, confirmed via the automated test suite.
Everything lives in a private Git repo; you’ll push to feature branches and open merge requests for review. Once merged and deployed to staging, we’ll verify together before promotion to production.