CODEWITHSUNDEEP
javascriptnode.jswebpack
DigitalDisaster
DigitalDisaster

Reputation: 517

Webpack doesn't show new build errors after a failure

Webpack stops and shows an error in the bundle. If I fix that error it will happily rebundle. If I fix an error and it finds another error it will not show the new error. It shows the first error. I have to kill webpack and re-run it to show the new error.

Any ideas how to always show the most recent error?

package.json webpack scripts command:

"dev": "webpack -d --watch --progress",

I'm running webpack run dev, and above is the dev command config

Upvotes: 0

Views: 689

Answers (1)

Agop
Agop

Reputation: 1917

Assuming that webpack is actually watching and reloading the files (check if the terminal scrolls down when you change one of your files), then it's probably something unusual going on with the way that your editor is saving your files.

For example, if your editor uses a "save and swap" technique, it's possible that webpack sees the old version of the file and loads that instead of the new version, thus showing you the original error. Check for editor settings related to "atomic saves" and such. The same situation can also be caused by temporary or backup files that your webpack configuration picks up as proper source files.

Upvotes: 1

Related Questions