Update 10-custom-server.mdx (vercel#63543)

Add description that custom servers cannot be applied to standalone output mode Co-authored-by: JJ Kasper <[email protected]> Co-authored-by: Steven <[email protected]>
onwidget · Mar 22, 2024 · 142b48f · 142b48f
1 parent 3a1be97
commit 142b48f
Showing 1 changed file with 1 addition and 0 deletions.
diff --git a/docs/03-pages/01-building-your-application/06-configuring/10-custom-server.mdx b/docs/03-pages/01-building-your-application/06-configuring/10-custom-server.mdx
@@ -17,6 +17,7 @@ By default, Next.js includes its own server with `next start`. If you have an ex
 >
 > - Before deciding to use a custom server, please keep in mind that it should only be used when the integrated router of Next.js can't meet your app requirements. A custom server will remove important performance optimizations, like **serverless functions** and **[Automatic Static Optimization](/docs/pages/building-your-application/rendering/automatic-static-optimization).**
 > - A custom server **cannot** be deployed on [Vercel](https://vercel.com/solutions/nextjs).
+> - Standalone output mode, does not trace custom server files and this mode outputs a separate minimal `server.js` file instead.
 
 Take a look at the following example of a custom server: