vercel/next.js · error

Fast Refresh had to perform a full reload due to a runtime e

Error message

Fast Refresh had to perform a full reload due to a runtime error.

What it means

Dev-server warning in hot-reloader-webpack's onHMR for the client-full-reload event: the browser reported a prior runtime error (hadRuntimeError), so Fast Refresh cannot safely apply the update incrementally — a broken module graph would persist. It logs this message while the client falls back to a full page reload to recover a clean state.

Source

Thrown at packages/next/src/server/dev/hot-reloader-webpack.ts:566

            }
            case 'client-removed-page':
            case 'client-added-page': {
              traceChild = {
                name: payload.event,
                attrs: { page: payload.page || '' },
              }
              break
            }
            case 'client-full-reload': {
              const { event, stackTrace, hadRuntimeError } = payload

              traceChild = {
                name: event,
                attrs: { stackTrace: stackTrace ?? '' },
              }

              if (hadRuntimeError) {
                Log.warn(FAST_REFRESH_RUNTIME_RELOAD)
                break
              }

              let fileMessage = ''
              if (stackTrace) {
                const file = /Aborted because (.+) is not accepted/.exec(
                  stackTrace
                )?.[1]
                if (file) {
                  // `file` is filepath in `pages/` but it can be a webpack url.
                  // If it's a webpack loader URL, it will include the app-pages layer
                  if (file.startsWith(`(${WEBPACK_LAYERS.appPagesBrowser})/`)) {
                    const fileUrl = new URL(file, 'file://')
                    const cwd = process.cwd()
                    const modules = fileUrl.searchParams
                      .getAll('modules')
                      .map((filepath) => filepath.slice(cwd.length + 1))
                      .filter(

View on GitHub (pinned to 258b1c1bc0)

Solutions

1. Fix the runtime error in your application; Fast Refresh reloaded the page to recover.

When it happens

Trigger: Thrown at packages/next/src/server/dev/hot-reloader-webpack.ts:567 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of vercel/next.js@258b1c1bc0 (2026-08-19). Data as JSON: /api/errors/a4cd14b757d32b73. Report an issue: GitHub.