Don't know how it happened, but VS2013 + NTVS RC2 got itself in a tizzy, and the project as a whole kept trying to refresh itself, over and over. An obvious manifestation of this was if I expanded a node in the Solution Explorer (say the npm node, and its subnodes), then a second or two later the tree would be collapsed, and the project item would become the selected item in the Solution Explorer. I expand the tree... then it collapses, over and over.
Closing then re-opening VS didn't solve. Only by rebooting the machine did I get it to stop doing this. Now I can't repro it... but I thought I'd mention it anyway, in case someone else has seen something like this.
Comments: > could you check what global packages you've installed? Bower. > Also, just to clarify - it's only children of the npm node that are an issue? Negative. > I'm hesitant to include a modal dialog for a few reasons: Another reason I suggested a modal is because, when the problem originally happened, I clicked on the Update menu item by mistake! My idea is that there could be a modal, a description of what will happen, a Start button to kick things off, and ofc the ability to cancel if you made a mistake in being there in the first place, like me.
Closing then re-opening VS didn't solve. Only by rebooting the machine did I get it to stop doing this. Now I can't repro it... but I thought I'd mention it anyway, in case someone else has seen something like this.
Comments: > could you check what global packages you've installed? Bower. > Also, just to clarify - it's only children of the npm node that are an issue? Negative. > I'm hesitant to include a modal dialog for a few reasons: Another reason I suggested a modal is because, when the problem originally happened, I clicked on the Update menu item by mistake! My idea is that there could be a modal, a description of what will happen, a Start button to kick things off, and ofc the ability to cancel if you made a mistake in being there in the first place, like me.