Accurate comparisons between monolithic and split packages

[dialing-up]

Currently the comparison view compares two packages selected directly by themselves, which gives something of a misleading picture when one software project has a monolithic package philosophy and the other has a "one package for each subsystem" philosophy.

For example is this comparison between vue and react, which doesn't give a accurate picture for react without the absolutely necessary platform binding (react-dom in the case of web)

I do not know if this is a real issue that can be solved without npmx making subjective judgements though.

[serhalp]

Hrm, I'm not sure this is something we could ever really "solve"...

Do you have any ideas?

[dialing-up]

The only idea I have is to track packages above a particular download threshold and see if they're always dependencies together in dependent packages, or maybe use peerDependencies for the same purpose

Though this would catch too many utility packages or dev-specifc I assume

[Codefoxdev]

It would also be tricky in the case of react, as you need to use react with both react-dom and react-native, so it also cannot automatically be added.
One possible solution could be to add some sort of tooltip that would prompt the user to change it to the specific platform bindings they are using? But then again, this would need to be tracked manually for specific packages.