feat: add support to filtering by workspaces #4
Conversation
There was a problem hiding this comment.
Mutating the tree is probably going to have some unfortunate effects. Better to get a list of what you care about, and only walk those portions of it. (This is also a fair bit cheaper, since it doesn't have to update edges or walk all the nodes.)
Also, the argument should be strictly workspace names. Allowing it to be either names or paths opens the door for ambiguity. (Consider a workspace named foo at the path ./bar, and a workspace named bar at the path ./foo. What does workspaces:['foo'] mean?) We use names everywhere else, since the CLI has that handy, and you have the tree anyway.
Definitely should not land this before you can get Arborist to just hand you a set of nodes that are relied on by some list of workspace names.
Adds support to a new `workspaces` option, that accepts an array of strings, allowing users to filter the resulting fund info to a specific set of workspaces and their dependencies. Relates to: npm/statusboard#301
ruyadorno
force-pushed
the
add-workspaces-filter
branch
from
3a82335
to
f38ea0c
Compare
Adds support to a new
workspacesoption, that accepts an array ofstrings, allowing users to filter the resulting fund info to a specific
set of workspaces and their dependencies.
References
Relates to: npm/statusboard#301