When the application has errors HMR slows down more and more

[vallemar]

The HMR works perfectly until you have errors in the code, when the application fails and when making a new change it starts again the HMR starts to work slower and slower until it is better to stop and start again. (vue 3)

[vallemar]

An easy way to replicate this problem is to add 2 times the class property to an element. Even now when I add 2 times this gets stuck and at the end it says that it has been updated but the changes no longer appear in the app. Example:

      <GridLayout
          class="asdf"
          class="rounded-full mx-2"></GridLayout>

It seems silly, but when you have many properties in an element, at least it usually happens to me

[rigor789]

Setting config.optimization.noEmitOnErrors(true); should make this better:

webpack.chainWebpack(config => {
  config.optimization.noEmitOnErrors(true);
})

This makes sure webpack doesn't emit any files when there are any compilation errors. This is not ideal in all cases, since you might still want to run the app when you have some small TS errors while developing/debugging.

Will be making a change to @nativescript/webpack to always emit the updated hash even if there are compilation errors, since in those cases currently the HMR hash chain is broken.