Invalid Segment Config

A route segment file (page, layout, or route handler) exports a segment config option with an invalid value. For example, dynamic must be one of 'auto', 'force-dynamic', 'error', or 'force-static'. Supplying an unsupported value triggers this error at build time.

References

nextjs.org/docs/messages/invalid-segment-config
nextjs.org/docs/app/api-reference/file-conventions/route-segment-config

In this namespace

← previous invalid-page-config Invalid Page Config next → metadata-base-not-set Metadata Base Not Set

cannot-override-metadata client-only-in-server-component duplicate-page invalid-page-config invalid-segment-config metadata-base-not-set missing-suspense-with-csr-bailout next-image-unconfigured-host next-script-for-ga no-html-link-for-pages