If you're working on a reasonably large JS app fighting circular dependencies, I just discovered "madge". It's a tool to analyze and detect all these circles. I wish I had known about this earlier... 😅 github.com/pahen/madge - ThreadSky

About ThreadSky

stefanjudis.com • 33 days ago

If you're working on a reasonably large JS app fighting circular dependencies, I just discovered "madge". It's a tool to analyze and detect all these circles.

I wish I had known about this earlier... 😅

https://github.com/pahen/madge

Comments

codey.bsky.social•32 days ago

paging @bjoerge.dev 📟🔊

lexiet.bsky.social•32 days ago

I've loved Madge for years, but I've always been hesitant to use it on all my projects because it's updated so rarely, and also the GraphJS dependency for visuals made it a hassle to just install and go.

I wish there was more static analysis tooling like this. Makes Clean Code much easier.

shaw.city•33 days ago

Madge was great for a short season in our codebase, but at the time it had some outdated dependencies (TypeScript maybe?) that caused our whole monorepo to fail.
https://blog.codepen.io/2023/01/25/398-devoops/#t=07:54

Hopefully they've updated so that's no longer a problem.

stefanjudis.com•33 days ago

That's good to know. Thanks!

I only tried a simple example because right now I'm lucky and don't face circular deps. 🫣

shaw.city•33 days ago

It's one of those problems that isn't a problem until it's a problem 😆 Compilers generally do a good job of resolving the circular dependencies but occasionally there's a line crossed that is tough to recover from. In those cases, Madge is a huge help.

stefanjudis.com•33 days ago

Trust me I've been there in the past. 😅

You import one file, everything falls apart and you spend hours (if not days) shuffling things around to get rid of the circle constantly fearing that there might be a major refactoring hiding under the cryptic errors.

I'm not missing these times. :D

runofthemillgeek.com•32 days ago

It was also very useful for creating dep graphs when I was working on a large multi-codebase refactor/split. Made it somewhat easier to understand some potential issues when moving some modules here and there or pruning items.

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply