vercel/next.js · error

[HMR] unexpected require(${module.id}) to disposed module

Error message

[HMR] unexpected require(${module.id}) to disposed module

What it means

In the JavaScript HMR runtime, warnUnexpectedRequire is called for modules that still require a disposed module after an update has been applied; it logs this warning to flag outdated references to replaced modules rather than throwing.

Source

Thrown at packages/next/src/bundles/webpack/packages/JavascriptHotModuleReplacement.runtime.js:112

				outdatedDependencies: outdatedDependencies
			};
		}

		function addAllToSet(a, b) {
			for (var i = 0; i < b.length; i++) {
				var item = b[i];
				if (a.indexOf(item) === -1) a.push(item);
			}
		}

		// at begin all updates modules are outdated
		// the "outdated" status can propagate to parents if they don't accept the children
		var outdatedDependencies = {};
		var outdatedModules = [];
		var appliedUpdate = {};

		var warnUnexpectedRequire = function warnUnexpectedRequire(module) {
			console.warn(
				"[HMR] unexpected require(" + module.id + ") to disposed module"
			);
		};

		for (var moduleId in currentUpdate) {
			if ($hasOwnProperty$(currentUpdate, moduleId)) {
				var newModuleFactory = currentUpdate[moduleId];
				/** @type {TODO} */
				var result = newModuleFactory
					? getAffectedModuleEffects(moduleId)
					: {
							type: "disposed",
							moduleId: moduleId
						};
				/** @type {Error|false} */
				var abortError = false;
				var doApply = false;
				var doDispose = false;

View on GitHub (pinned to 0eb3775416)

Solutions

1. Reload the page; the module graph changed and an old module reference was used after disposal.

When it happens

Trigger: Thrown at packages/next/src/bundles/webpack/packages/JavascriptHotModuleReplacement.runtime.js:112 when the library encounters an invalid state.

Common situations: See trigger scenarios.

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