Nothing's as fun as unraveling the mystery of how a certain dependency got pulled in transitively....

In a monolith.

With over 1000 dependencies.

Kinda like sorting rice by the size of each grain.

Things that make a friday entertaining.


  • 0
    Its the best part of being a dev lol
  • 1
    I'm sure you already did this but the command "yarn why" can help a little with showing which dep is responsible for some other dep existing or having a certain version.

    as in "yarn why leftpad"

    Not great though..once had to figure out why v1 instead of v2 of a package was used and it didn't really help me get to the bottom of it.
  • 0
    @jiraTicket Its not a JS project....


    But yeah, I did more or less the same, just with SBT.
Add Comment