NPE in FileSystemInfo

[HitkoDev]

Bug report

What is the current behavior?

Null pointer error Error due to null object in FileSystemInfo.getContextTimestamp

If the current behavior is a bug, please provide the steps to reproduce.

Call FileSystemInfo.getContextTimestamp with an immutable path (immutable path prefixes are provided in FileSystemInfo constructor).

What is the expected behavior?

_readContextTimestamp (processor for contextTimestampQueue) returns null for immutable paths:

webpack/lib/FileSystemInfo.js

Lines 3016 to 3020 in bd7cb37

	_readContextTimestamp(path, callback) {
	this._readContext(
	{
	path,
	fromImmutablePath: () => null,

so the queue callback in getContextTimestamp should handle entry possibly being null:

webpack/lib/FileSystemInfo.js

Lines 1164 to 1168 in bd7cb37

	this.contextTimestampQueue.add(path, (err, entry) => {
	const resolved = getResolvedTimestamp(entry);
	if (resolved !== undefined) return callback(null, resolved);
	this._resolveContextTimestamp(entry, callback);
	});

Other relevant information:
webpack version: 5.51.0
Node.js version: all
Operating System: all
Additional tools: N/A

[HitkoDev]

Related: #14019

[alexander-akait]

What is Null pointer? It is not Java

[HitkoDev]

What is Null pointer? It is not Java

True, JavaScript has "nullable types" instead of "null pointers", and typeof null === "object", so technically I should say "null object error" (NOE) or "error due to null object" (EDTNO). But perhaps enough nitpicking, let's focus on the fact that callback receives null and doesn't handle it.

[kandangit]

I also have this problem

FileSystemInfo.js:816
        if (entry.resolved !== undefined) return entry.resolved;
                 ^

TypeError: Cannot read property 'resolved' of null

This looks like a recent webpack update (webpack is imported as a transitive dependency in my Node project).

Version 5.51.0 gives the issue. I have resolved by importing a previous dependency directly:

"webpack": "5.45.1"

[HitkoDev]

This looks like a recent webpack update. (use webpack as a transitive dependency in my Node project).

It appeared in 5.51.0, so just downgrade to 5.50.0 for now.

[sokra]

Yep that is a bug. Could one of you give me a stack trace of that?

[HitkoDev]

Yep that is a bug. Could one of you give me a stack trace of that?

TypeError: Cannot read property 'resolved' of null
    at getResolvedTimestamp (node_modules/webpack/lib/FileSystemInfo.js:816:12)
    at node_modules/webpack/lib/FileSystemInfo.js:1165:21
    at node_modules/webpack/lib/util/AsyncQueue.js:352:5
    at Hook.eval [as callAsync] (eval at create (node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (node_modules/tapable/lib/Hook.js:18:14)
    at AsyncQueue._handleResult (node_modules/webpack/lib/util/AsyncQueue.js:322:21)
    at node_modules/webpack/lib/util/AsyncQueue.js:305:11
    at node_modules/webpack/lib/FileSystemInfo.js:3100:5
    at Array.<anonymous> (node_modules/webpack/lib/FileSystemInfo.js:2960:13)
    at runCallbacks (node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:27:15)