mkellsy
commented
3 years ago The close button is hidden for a reason. I traced every path, and the dialog will close with a success or it will alert an error. Yarn during network disruptions, will retry, a lot. It can take up to 10 minutes for Yarn to give up. Once it does, the error will show.
To correct this, I am changing the window controls to be persistent. This is already in a different issue, so I am closing this one.
as npm was down for some minutes today i tried to install the ring plugin to see what happens here are the screenshots
Using windows app theres no way to escape the screen when an error occurs
if there is an close windows X on the top right of the popup that would be great. but if a user closes the popup window the command should stay running in background