Outline updated November 2026
React Apps with Next.js
Class Duration
35 hours of live training delivered over 5 days.
Student Prerequisites
- Experience with modern JavaScript or TypeScript
- Working knowledge of modern language features such as classes, modules, arrow functions, and destructuring
- No prior React or Next.js experience required
Target Audience
Web developers and teams new to React who will build applications on Next.js with the App Router. It also suits teams maintaining Pages Router code or the older caching model. Teams that want more client-side depth afterward can continue to Advanced React.
Description
This course teaches React and Next.js to developers new to React. It starts with components, JSX, props, events, and hooks, then moves to the App Router, Server Components, and Server Actions. New apps from create-next-app enable Cache Components, so students learn 'use cache', cacheLife, and tag-based invalidation. Later modules cover proxy.ts, streaming with Suspense, testing with Vitest and Playwright, and deployment. A security module treats every Server Action as a public endpoint and covers patching after advisories.
Learning Outcomes
- Build React function components with JSX, props, events, and hooks.
- Build a Next.js app on the App Router with Server and Client Components.
- Handle forms and mutations with Server Actions and React's form hooks.
- Let the React Compiler handle memoization.
- Cache functions and components with
'use cache'andcacheLifeprofiles. - Invalidate cached data with
cacheTag,revalidateTag,updateTag, andrefresh. - Design routes as a static shell with streamed dynamic content.
- Migrate code that relies on implicit fetch caching and route segment config.
- Intercept and rewrite requests with
proxy.ts. - Secure Server Actions with authorization, input validation, and prompt patching.
- Test with Vitest, React Testing Library, and Playwright.
- Deploy to Vercel, Cloudflare, AWS, or self-hosted Node.js.
Training Materials
Comprehensive courseware is distributed online at the start of class.
Software Requirements
Students will need a free, personal GitHub account to access the courseware. Students will need permission to install Node.js and Visual Studio Code on their computers. Also, students will need permission to install NPM Packages and Visual Studio Code extensions. If students are unable to configure a local environment, a cloud-based environment can be provided.
Versions covered: Next.js 16 (16.4 or later) with React 19.3 on a current Node.js LTS release.
Training Topics
React and Next.js Overview
- What problem does React solve?
- What problem does Next.js solve?
- How the Next.js model has changed
- App Router vs. Pages Router
- Reading legacy Pages Router code
- Why new apps start with Cache Components
Development Environment
- Node.js LTS
- Visual Studio Code with React DevTools
- Next.js CLI and
create-next-app - Turbopack as the default bundler
Project Setup
- Creating a project with
create-next-app - Folder structure under
app/ - Browser support
- Styles and assets
- Dependencies and
next.config.ts
React Components
- Function components only
- Composition and reuse
- Automatic memoization with the React Compiler
Rendering and JSX
- What problem does JSX solve?
- Embedding expressions, attributes, fragments
- Virtual DOM and Fiber
- Conditional rendering
- Rendering lists with
key
Component Props
- Immutable props
- String literals vs. expressions
- Typing props with TypeScript
- Default prop values
- Naming patterns
Events and Actions
- DOM events
- Event handlers in function components
- Passing handlers via props
- React Actions for form submissions
React Hooks
useStateanduseEffectuseCallbackanduseMemo- When the Compiler removes the need
useOptimisticfor optimistic UIuseActionStateanduseFormStatususefor promises and context- Custom hooks
Forms with Server Actions
- Controlled and uncontrolled components
- Server Actions with
<form action> - The
'use server'directive - Validation with Zod
- Forms that work without JavaScript
Component Architecture
- Server vs. Client Components
- The
'use client'boundary - Reusable components and communication
- Container and presentation patterns
- Avoiding
'use client'everywhere
App Router
- Defining routes under
app/ page.tsxandlayout.tsxloading.tsx,error.tsx, andnot-found.tsx- Navigation and prefetching with
<Link> - Dynamic routes and
generateStaticParams - Route groups
- Parallel and intercepting routes
- Request interception with
proxy.ts
Data Fetching
- Fetching data in Server Components
- Request deduplication with React
cache() - Runtime APIs such as
cookies()andheaders() searchParamsandconnection()- Server Functions for mutations
- Connecting forms to Server Actions
Rendering with Cache Components
- The static shell
- Streaming dynamic content with Suspense
- Partial Prerendering as the default model
- Partial Prefetching
- Static guarantees with
ensureStatic - Client-side rendering for interactive UIs
- Reading build output
Caching with Cache Components
- Enabling
cacheComponents - The
'use cache'directive - Built-in
cacheLifeprofiles - Custom stale, revalidate, and expire times
- Tagging entries with
cacheTag revalidateTagandrevalidatePath- Read-your-own-writes with
updateTag - Refreshing the client with
refresh 'use cache: private'for request data'use cache: remote'for shared caches- Migrating from
unstable_cache - Replacing
dynamicandrevalidatesegment options
Security
- Server Components security advisories
- Remote code execution and denial of service
- Scheduled Next.js security releases
- Supported release lines and dependency scanning
- Server Actions as public endpoints
- Authorization inside every action
- Input validation and allowed origins
- Encrypted closures and action IDs
- A data access layer and
server-only - The experimental taint APIs
- Responding to an advisory
Styling
- Tailwind CSS
- CSS Modules
- CSS-in-JS with Server Components
- Sass
- Responsive design
Testing
- Vitest and React Testing Library
- Mocking Server Actions
- Testing Server Components
- Playwright for end-to-end tests
- Visual regression with Playwright snapshots
Deployment
- Vercel
- Cloudflare with
@opennextjs/cloudflare - AWS and self-hosted Node.js
- Platform adapters and the Adapter API
- Static export