You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 4, 2023. It is now read-only.
Hello, i started to use this plugin, but when any warning/error is printed to the console it is printed to the end of webpack stack like this, and i have to scroll 400 lines to the up to see real warnings
I was experimenting with this source
// Hook into the compilation as early as possible, at the seal stepcompilation.plugin('seal',function(){// We need to keep the reference to the compilation's scopevar_this=this;// Errors/Warnings are pushed to the compilation's error handling// so we can drop out of the processing tree on warn/errorreport.forEach(function(x){if(x.error){_this.errors.unshift(x.file);}else{_this.warnings.unshift(x.file);}});
and changed seal to the done now i get expected result in console
Is there any particular reason to hook into seal step? If not it is possible to change this or open PR with this? Thanks
The text was updated successfully, but these errors were encountered:
Hello, i started to use this plugin, but when any warning/error is printed to the console it is printed to the end of webpack stack like this, and i have to scroll 400 lines to the up to see real warnings
I was experimenting with this source
and changed
seal
to thedone
now i get expected result in consoleIs there any particular reason to hook into seal step? If not it is possible to change this or open PR with this? Thanks
The text was updated successfully, but these errors were encountered: