Add support for workspace projects

[slheavner]

npm ls for workspace projects include the "root" project, resulting in ropm including the workspace project as a dependency of itself, and adding postfixes (_v1, etc.) to its actual dependencies

How:

• use --json for npm ls instead of --parseable
• iterate items in the json dependency try until we find the matching name field
• use that item as the "root" dependency graph
• flatten the json to match the original file path format

[TwitchBronBron]

One of the unit tests is failing in the CI, so can you take a look at that?

Also, does this change need to account for aliases (when we install some package with a different name)?

[slheavner]

One of the unit tests is failing in the CI, so can you take a look at that?

Also, does this change need to account for aliases (when we install some package with a different name)?

I think I got caught by mac's case-insensitive file system 🤦

The name comparison here doesn't touch the dependencies, it's only comparing the "host" package name to make sure it is used as the root dependency in the graph, so those aliases shouldn't apply

[TwitchBronBron]

Looks like it's still failing.

[TwitchBronBron]

oh wow, I completely forgot about this! I'll try and give it a good review this week. Sorry about that!

[slheavner]

no worries, revisiting.

There the problem with CI is the npm version tagged there vs what I was testing against. I need to dig into the differences and find what's causing it.

[slheavner]

workflow passed on my fork, should be good to go

[TwitchBronBron]

I'm so sorry this fell through the cracks for so long. Do you mind taking a look at the merge conflicts and letting us know if this is still something that is needed?

Also, I'm not entirely familiar with "workspace projects", so do you mind giving a quick overview of that that actually means? Once I have a better understanding of what this solves, I'm happy to merge it and cut a release.