You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! Super handy tool, I'm a big fan! From what I've seen so far, it's possible to have two listings for the same package if said package has multiple version dependencies.
What I'd like to propose is that an --aggregate parameter be added, which would produce the following (in this example):
@react-native/debugger-frontend
It could check the license fields: if the license text or other data were different, it wouldn't aggregate those together. But for packages that the ony difference is version, it could just lump all those together.
The text was updated successfully, but these errors were encountered:
Hello! Super handy tool, I'm a big fan! From what I've seen so far, it's possible to have two listings for the same package if said package has multiple version dependencies.
For example:
What I'd like to propose is that an --aggregate parameter be added, which would produce the following (in this example):
It could check the license fields: if the license text or other data were different, it wouldn't aggregate those together. But for packages that the ony difference is version, it could just lump all those together.
The text was updated successfully, but these errors were encountered: