Repository navigation
Differentiate dev_dependencies and dependencies #3202
Description
Related to #3095 a little.
As a package author, it's important to me that I don't drag in too many dependencies for my consumers. The more packages I need, the more risk of version conflict. On the other hand, during development time, there's no cost to me adding packages.
It would be great if the Dependencies toolwindow was able to disambiguate these two classes of package dependency. For example, it could be a filter to say "only show runtime dependencies", or perhaps a different icon (although this would be tristate, since some packages may be transitively depended on in both development and runtime scenarios).
See image below as an example:
Activity
DanTup commentedon Mar 15, 2021
Makes sense. Perhaps listing deps at the top level and then the final item is a "dev_dependencies" folder that contains the others?
There's a PR in progress to add JSON output as discussed in #3095 which looks to include a
kindagainst each dep (ofdirectordev), so it should be easy to handle these both from the same data source.sigurdm commentedon Mar 15, 2021
Also consider transitive dependencies as a third category.
DanTup commentedon May 25, 2021
When using a Dart SDK >= v2.14.0 the dependencies will now be split into folders for direct/dev/transitive dependencies: