Q40: What was target: 'serverless' in legacy Next.js Pages Router builds?
Legacy Next.js builds offered target: 'serverless', compiling every page inside pages/ into an independent self-contained Node.js Lambda function rather than a single monolithic server instance. (Deprecated in modern versions in favor of automatic Vercel serverless splitting).
Key Takeaways
- Compiled individual pages into standalone isolated Lambda functions.
- Replaced by modern automatic serverless platform slicing.
Knowledge Check
Why was target: 'serverless' historically useful for cloud deployments?