Closed dzearing closed 7 years ago
@alanshaw Awesome, thanks!
@alanshaw Would it be worthwhile to keep that one open as a feature request for parsing lerna.json and coming up with an aggregate status of all packages?
So having multiple (5+) package.json fils it would be really nice to have an aggregated badge. [Showing 10+ badges (dependencies + devDependencies) will probably defeat its purpose.
However, it seems this might be a bit out of scope for david dm... or is there any plan for something like this? (e.g. search through all files and pick up the package.json ones) I'm just curious :)
We have repos which contain multiple package.jsons. These repos use tools such as @microsoft/rush or lerna to manage installing dependencies, linking, building, and publishing them. Babel, React, Angular, Ember, Meteor, Jest, and many others develop all of their packages within a single repository.
For example, same repo, 2 different folders with package.json:
https://github.com/OfficeDev/office-ui-fabric-react/tree/master/packages/office-ui-fabric-react https://github.com/OfficeDev/office-ui-fabric-react/tree/master/packages/utilities
Is there a way that David can generate badges for these? At a minimum, just be able to generate a badge for each of the packages, but ideally generate a single badge for the repo's README.md which can track all the dependencies in the entire repo. (If there needs to be some metadata in the root package.json to make that work, cool.)
I tried a few variations without any luck:
https://david-dm.org/OfficeDev/office-ui-fabric-react/packages/office-ui-fabric-react.svg https://david-dm.org/OfficeDev/office-ui-fabric-react/tree/master/packages/office-ui-fabric-react.svg