It would be handy to be able to indicate somewhere in the pubspec when a package is _usually_ a dev dependency.
@jonasfj we could infer this from the pubspec.yaml files: if a package is 90%+ referenced only as part of the dev_dependencies:, we could display the different label. However, it should be probably part of the package dependency graph or search.
We could also make a convention install.md is render there if present..
install.md sounds good, and/or we could also extract it from readme (if we had the parsing and table-of-content extraction for it).
Can we bump the priority of this issue? We're likely going to reference the installing page for package:test from tooling and docs, and it currently provides incorrect guidence.
https://pub.dev/packages/test#-installing-tab-
Even one-off handling pf package:test would be a useful workaround (if a general purpose solution isn't feasible in the near term).
@devoncarew: I've submitted #3397 to simply change the dependencies to dev_dependencies in the case of package:test. Is there any other urgent part to be fixed?
Nope, that's it; thanks!
Most helpful comment
It would be handy to be able to indicate somewhere in the pubspec when a package is _usually_ a dev dependency.