Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filter dependencies by organization #47

Open
bennycode opened this issue Feb 2, 2021 · 4 comments
Open

Filter dependencies by organization #47

bennycode opened this issue Feb 2, 2021 · 4 comments

Comments

@bennycode
Copy link

First of all, I really like npmgraph. It's dependency visualization is of great value!

Would it be possible to add a filter for an organization?

I would like to be able to only see the dependencies that are from my organization. For example, when I look for @wireapp/core, I want to just see the dependencies that start with @wireapp, so it will show me @wireapp/api-client, @wireapp/cryptobox, etc. but not tough-cookie or any other dependency which doesn't belong to my organization.

Testing Example: https://npm.broofa.com/?q=@wireapp/core

@fregante
Copy link
Member

fregante commented Feb 4, 2021

Related: #38

@bennycode
Copy link
Author

It's kind of related... I don't want to focus the organization. I want to filter everything which is not from the organization. I checked out the repo locally and applied a small adjustment which works for me:

image

@broofa, how about making this an option in the section of the switches? I can see "Include" options and we could add "Exclude" options too. There is also a listing of "Modules", "Maintainers" & "Licenses"... How about adding a fourth for "Organizations"?

@bennycode
Copy link
Author

Here is a mockup of how I would like to filter it:

image

@imbeyondboredom
Copy link

Bumping this. Would love to be able to exclude packages that are outside of my org. I want to be able to provide wider org visibility on what level of regression needs to happen when someone updates a dependency. Or at least show the potential impact to a developer when they're about to change something in a monorepo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants