Client reloads app even when there is an error and the screen is just shown for a very short time.

[jespermjonsson]

When loading the application with the live client e.g. http://localhost:3000/webpack-dev-server/index.html the browser is reloaded on script/style changes. But when there is an syntax error (and using the NoErrorsPlugin) the browser is reloaded with the message: Errors while compiling. App ready. And an error screen is displayed just before the browser is reloaded. But if the browser is reloaded manually after this syntax error has occured (so it is the initial load) the error screen is displayed nicely with the title: Errors while compiling. App updated with errors. No reload!.

Is there a reason why the client reloads the browser on errors? Thinking of these lines in the client:

webpack-dev-server/client/index.js

Lines 47 to 48 in 8fddb2a

	if(initial) return initial = false;
	reloadApp();

Or are you open to change this somehow so the error message is shown until the syntax error is fixed and a new bundle is generated even when the error occurs during a regular reload (not just the initial load)?

[SpaceK33z]

More then one year later, I fixed this in the prevent-reload-on-errors branch ⏳ .

I simply removed the code that did a reload when there were warnings or errors. I still want to look at it if there are valid use cases for this. At the moment I can't think of any.

[SpaceK33z]

Looks like this code was introduced in the first version of the "inline" modus (2329516). After some tests it seems safe to remove.

[kozakl]

Hello, I use react + typescript and when I for example load module without dt.ts definition file I see error in console and reload is prevented...
So reloading app when compiler see errors should be optional because IT'S errors usually are not dangerous, but stopping hot reload is really uncomfortable...