webpack/webpack · error · Error

No input filesystem provided

Error message

No input filesystem provided

What it means

Error "No input filesystem provided" thrown in webpack/webpack.

Source

Thrown at lib/WebpackOptionsApply.js:1054

					}
					break;
				}
				default:
					// @ts-expect-error Property 'type' does not exist on type 'never'. ts(2339)
					throw new Error(`Unknown cache type ${cacheOptions.type}`);
			}
		}
		new ResolverCachePlugin().apply(compiler);

		if (options.ignoreWarnings && options.ignoreWarnings.length > 0) {
			const IgnoreWarningsPlugin = require("./IgnoreWarningsPlugin");

			new IgnoreWarningsPlugin(options.ignoreWarnings).apply(compiler);
		}

		compiler.hooks.afterPlugins.call(compiler);
		if (!compiler.inputFileSystem) {
			throw new Error("No input filesystem provided");
		}
		compiler.resolverFactory.hooks.resolveOptions
			.for("normal")
			.tap(CLASS_NAME, (resolveOptions) => {
				resolveOptions = cleverMerge(options.resolve, resolveOptions);
				resolveOptions.fileSystem =
					/** @type {InputFileSystem} */
					(compiler.inputFileSystem);
				return resolveOptions;
			});
		compiler.resolverFactory.hooks.resolveOptions
			.for("context")
			.tap(CLASS_NAME, (resolveOptions) => {
				resolveOptions = cleverMerge(options.resolve, resolveOptions);
				resolveOptions.fileSystem =
					/** @type {InputFileSystem} */
					(compiler.inputFileSystem);
				resolveOptions.resolveToContext = true;

View on GitHub (pinned to 318421ea8a)

Solutions

1. Provide an inputFileSystem when invoking webpack programmatically; the default Node.js filesystem is used when running via the CLI.

When it happens

Trigger: Thrown at lib/WebpackOptionsApply.js:1054 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of webpack/webpack@318421ea8a (2026-08-03). Data as JSON: /data/errors/52777d050689a51d.json. Report an issue: GitHub.