Nuxt.js: Console errors don't disappear after fixing

[romikzo]

Version

v2.0.0

Reproduction link

http://localhost:3000

Steps to reproduce

Follow the instructions in nuxt.js repo README.md:
1) yarn add nuxt
2) add scripts: {"nuxt": "nuxt"} to package.json
3) add file pages/index.vue with content

<script>
export default {
}
</script>

4) yarn run nuxt

Then try to remove } in pages/index.vue. You will see error in terminal. After return } back, error in terminal not disappear and HMR will cease work.

What is expected ?

Nuxt should see that i fix error and show success inscription.

What is actually happening?

Error stay

_{This bug report is available on Nuxt community (#c7833)}

[manniL]

~Can not reproduce.~

[manniL]

[romikzo]

Error in terminal disappear too?

[romikzo]

Look at the console: https://glitch.com/edit/#!/join/bec57521-10a6-419d-9a08-3cc694b58de0

[manniL]

Ah, gotcha. The error will stay in console.
This is only a visual bug though as HMR will continue to work (as shown in the GIF)

[baumannzone]

Same issue, reported here:
https://stackoverflow.com/questions/52715349/linter-eslint-keep-errors-after-fix-them-in-nuxt-app

It looks like you can keep working, but for newcomers users it's very confusing

[gapipro]

Yea, same issue happens to me also. It's really annoying, because in terminal you normally check if everything is compiled correctly.

[zlzdp]

same issue, the last eslint error message not auto remove when I fixed for eslint.

[stale[bot]]

Thanks for your contribution to Nuxt.js!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of nuxt-edge
2. Comment the steps to reproduce it

Issues that are labeled as 🕐Pending will not be automatically marked as stale.

[manniL]

There is no screen clearing anymore ;)
https://github.com/nuxt/webpackbar/releases

[evry-johber]

@manniL Can you elaborate how that update affects this issue? I tried using Nuxt 2.32 in spa-mode and get "compiled successfully" regardless of any errors in my files. Do I need to adjust my config?

[manniL]

Errors will be clearly shown but there is no screen clear anymore ;)

[evry-johber]

@manniL I see, thanks for elaborating. This is my current result in spa-mode:

[manniL]

@evry-johber That's strange :thinking: Could you open an issue for webpackbar here? Please include your editor and as much info as possible :relaxed:

[evry-johber]

@manniL Sure, I'll see what I can do to create a minimal reproducible example

[evry-johber]

@manniL Hmm, did a fresh npx create-nuxt-app, did the very same change as you did in universal mode, and still no error reported. I'm using Node 10.13 on Windows 10. Should be enough to add eslint in the create-nuxt-app wizard, right?

[manniL]

@evry-johber That should even work without eslint as a component couldn't be found while building :thinking:

[evry-johber]

@manniL It seems to work fine after a reboot :) Is there any way to capture more errors in the output window? For example, if I change components: { Logo } to components: { Logo123 }, it still compiles successfully, despite having eslint enabled.

[manniL]

Sure. Make your eslint-config more strict ;)

I'd suggest our setup (https://github.com/nuxt/eslint-config)

Prod example: https://github.com/manniL/lichter.io/blob/master/.eslintrc.js

[evry-johber]

@manniL Aaah, thank you!!

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.