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

See common 3rd party dependencies between workspace packages #2

Open
jrschumacher opened this issue Nov 28, 2023 · 2 comments
Open

Comments

@jrschumacher
Copy link

jrschumacher commented Nov 28, 2023

I want to visualize common 3rd party deps, so I can see which deps are lynch pins and eliminate one-off deps to reduce supply chain attacks.


I saw that in antoine-coulon/skott advanced dependency graph functionality not found in rush-plugin-skott. Is it trivial to update to the latest skott and get those features?

@antoine-coulon
Copy link
Owner

antoine-coulon commented Nov 29, 2023

Hey @jrschumacher,

Just want to be sure, when you're talking about 3rd party dependencies visualisation you talk about 3rd party dependencies by project? skott does actually implement that but each 3rd party dep is attached to a single JS/TS module, the goal with Krush would be to provide a visualisation but per Rush project instead of per module.

If you're talking about that specifically (Rush integration) the work was already started by me in the past but was not released because it was requiring upstream work on skott side and I unfortunately hadn't the time to do so (I was focused on releasing skott related features, such as the brand new release of the web app). Given I'm lately investing time again for Rush's ecosystem and that skott is pretty stable, I might end up releasing all this by the end of the month.

@antoine-coulon
Copy link
Owner

Note also that I'm interesting in collecting feedback if you are willing to rely on the plugin for your Rush setup in the future :)

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

2 participants