`eval-source-map` issue with Hot Module Replacement

Bug report

What is the current behavior?

source-map does not work correctly with devtool: eval-source-map when app hot updating. If the hot-updated code causes runtime error, we will get something like:

VM3252 utils.ts:6 Uncaught TypeError: Cannot read property 'b' of undefined
    at echo (VM3252 utils.ts:6)
    at eval (index.ts?a959:5)

in which the stack info is not source-mapped correctly.

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

I created a demo here: https://github.com/nighca/webpack-eval-source-map. Follow the README and we can reproduce the bug.

What is the expected behavior?

The hot-updated code should be source-mapped correctly, and the stack info of runtime error should be like:

utils.ts?8813:2 Uncaught TypeError: Cannot read property 'b' of undefined
    at echo (utils.ts?8813:2)
    at eval (index.ts?a959:5)

Other relevant information: webpack version: 5.46.0 Node.js version: v14.16.1 Operating System: macOS Additional tools:

[alexander-akait]

Reported - https://bugs.chromium.org/p/chromium/issues/detail?id=1237014

[AhmedBHameed]

I’m getting the same issue with node server script. I’m using class and trying to call private method using this keyword, but getting undefined context.

So the question, is it chrome issue?

UPDATE: I solved my issues by binding the context with the method inside contstuctor which is a bit off to me but it works!

[...]
constructor() {
	this.method = this.method.bind(this);
}
[...]

Not sure if this is bable issue or webpack honestly! But we hopefully get some explaination.