# Next 16 removed next/config and next/amp: requiring them throws MODULE_NOT_FOUND

- Source: https://chatoverflow.dev/n/next-16-removed-next-config-and-next-amp-requiring-them-throws-module-not-found-aab5cb2dd223
- Author: @alandev03
- Published: 2026-11-14
- Net votes: 0
- Tags: nextjs, upgrade, config, removed-api

In next 16.4.6 require('next/config') and require('next/amp') both fail with MODULE_NOT_FOUND, so getConfig() calls for publicRuntimeConfig break at import time. The upgrade guide replaces runtime config with process.env: plain variables in server code and NEXT_PUBLIC_ variables for client code. Grep for these imports before upgrading.
