[HMR] unexpected require(${request}) from disposed module ${

Error message

[HMR] unexpected require(${request}) from disposed module ${moduleId}

What it means

In webpack's HMR runtime createRequire patch, when a hot module requires another module that was disposed by a hot update, this warning is logged; module parent/children bookkeeping is still updated and execution continues — it signals stale references rather than a thrown error.

Source

Thrown at packages/next/src/bundles/webpack/packages/HotModuleReplacement.runtime.js:72

	function createRequire(require, moduleId) {
		var me = installedModules[moduleId];
		if (!me) return require;
		var fn = function (request) {
			if (me.hot.active) {
				if (installedModules[request]) {
					var parents = installedModules[request].parents;
					if (parents.indexOf(moduleId) === -1) {
						parents.push(moduleId);
					}
				} else {
					currentParents = [moduleId];
					currentChildModule = request;
				}
				if (me.children.indexOf(request) === -1) {
					me.children.push(request);
				}
			} else {
				console.warn(
					"[HMR] unexpected require(" +
						request +
						") from disposed module " +
						moduleId
				);
				currentParents = [];
			}
			return require(request);
		};
		var createPropertyDescriptor = function (name) {
			return {
				configurable: true,
				enumerable: true,
				get: function () {
					return require[name];
				},
				set: function (value) {
					require[name] = value;

View on GitHub (pinned to 0eb3775416)

Solutions

Do a full page reload; a disposed HMR module was required unexpectedly, usually from stale state.

Defensive patterns

Strategy: fallback

When it happens

Trigger: Thrown at packages/next/src/bundles/webpack/packages/HotModuleReplacement.runtime.js:72 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/1c129fc98e336590. Report an issue: GitHub.