To disable this behavior and prevent routing based on files in pages, open and disable the useFileSystemPublicRoutes config: module. If your project uses a custom server, this behavior may result in the same content being served from multiple paths, which can present problems with SEO and UX. Disabling file-system routingīy default, Next will serve each file in the pages folder under a pathname matching the filename. The returned app can then be used to let Next.js handle requests as required. Take a look at the following example of a custom server: // server.js const A custom server will remove important performance optimizations, like serverless functions and Automatic Static Optimization.
Note: A custom server cannot be deployed on Vercel.īefore 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. Most of the time, you will not need this – but it's available for complete customization. A custom Next.js server allows you to start a server 100% programmatically in order to use custom server patterns. If you have an existing backend, you can still use it with Next.js (this is not a custom server). By default, Next.js includes its own server with next start.
0 kommentar(er)
