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
Please provide a description of the bug / issue, and provide the details below:
I'm not sure if this is related to node 11, but I believe it started happening after upgrading to node 11, I was previously running node 10 where it was working fine. webpack-dashboard gets stuck at 67-69% progress. Nothing happens when trying to quit with the "q"-key. It's still serving the page though, so webpack-dev-server seems to still run properly in the background. There's a node process running at >99% CPU usage, killing the process fills the terminal with the symbols shown in the screenshot below.
I'm not sure if this is related to node 11, but I believe it started happening after upgrading to node 11, I was previously running node 10 where it was working fine. webpack-dashboard gets stuck at 67-69% progress. Nothing happens when trying to quit with the "q"-key. It's still serving the page though, so webpack-dev-server seems to still run properly in the background. There's a node process running at >99% CPU usage, killing the process fills the terminal with the symbols shown in the screenshot below.
====================================================================
If the issue is visual, please provide screenshots here
====================================================================
Steps to reproduce the problem
Run webpack-dashboard with the package.json script below
====================================================================
Please provide a gist of relevant files
====================================================================
More Details
What operating system are you on?
macOS Mojave 10.14
What terminal application are you using?
Apple's Terminal app
What version of webpack-dashboard are you using?
2.0.0
What is the output of running
echo $TERM
?xterm-256color
The text was updated successfully, but these errors were encountered: