When opening a medium-sized web project, the left-side tree in task runner explorer is filled with a considerable amount of nodes, and most of them are "just noise". This makes it hard to find a task I would manually like to run.
This was not a problem when task runner explorer only handled grunt and gulp since there were much less nodes to deal with.
NPM Scripts Task Runner is mainly at fault here especially because of the uninstall nodes. There tend to be many of them and they are very rarely used (and even less frequently bound to VS events, like Before Build, etc.).
Steps to recreate
Create a project with a considerable amount of npm packages.
Use something like grunt too for good measure.
Reopen the solution.
Try to find the 2 specific tasks you like to run manually every now and then.
Scroll a lot every time.
Current behavior
All of the nodes are open by default. This was fine with 10-15 tasks, but now it's starting to get tedious to use.
Expected behavior
By default close all nodes in the tree that are not "Custom" (that means the "Defaults" nodes). Or if it's not possible all the nodes should be closed by default.
The state of the tree should be remembered between multiple VS sessions. Therefore if I organize it the way I want my settings would not be lost every time I reopen VS.
Or make it possible to pin specific tasks at the top.
EDIT: I realize that this turned out a bug report for Task Runner Explorer, not just NPM Task Runner, but since there is NPM specific stuff in it too, and I can't find where to report bugs for Task Runner Explorer directly, let me leave it here.
Installed product versions
Description
When opening a medium-sized web project, the left-side tree in task runner explorer is filled with a considerable amount of nodes, and most of them are "just noise". This makes it hard to find a task I would manually like to run.
This was not a problem when task runner explorer only handled grunt and gulp since there were much less nodes to deal with.
NPM Scripts Task Runner is mainly at fault here especially because of the uninstall nodes. There tend to be many of them and they are very rarely used (and even less frequently bound to VS events, like Before Build, etc.).
Steps to recreate
Current behavior
All of the nodes are open by default. This was fine with 10-15 tasks, but now it's starting to get tedious to use.
Expected behavior
By default close all nodes in the tree that are not "Custom" (that means the "Defaults" nodes). Or if it's not possible all the nodes should be closed by default.
The state of the tree should be remembered between multiple VS sessions. Therefore if I organize it the way I want my settings would not be lost every time I reopen VS.
Or make it possible to pin specific tasks at the top.
EDIT: I realize that this turned out a bug report for Task Runner Explorer, not just NPM Task Runner, but since there is NPM specific stuff in it too, and I can't find where to report bugs for Task Runner Explorer directly, let me leave it here.