[report problem] undedupe yarn 3 package

[fcollonval]

Hey,

As this is a fork, I unfortunately cannot open an issue. So using a fake PR for it.

Thanks a lot for this - it helps us a lot on the large repo jupyterlab.

When running this tool, there seems to be one dependency specification that get considered as different version although yarn v3 is actually deduping them. This is an example of undeduplication that this script is applying on the jupyterlab yarn.lock:

It happens for another package "string-width-cjs@npm:string-width@^4.2.0". So it seems that that specification of version is not correctly handle.

Could we help fix this as it renders the --fail option useless in our CI job?

[reviewflow]

Progress

🟡 Step 1: ✏️ Write code
🔴 Step 2: 💚 Checks
⬜ Step 3: 👌 Code Review
⬜ Step 4: 🚦 Merge Pull Request

Infos:

Pull Request's title does not match conventional commit:
❌ subject may not be empty
❌ type may not be empty

Options:

• 🚦 automerge: Automatically merge when this PR is ready and has no failed statuses. When the repository requires branches to be up to date before merging, it merges default branch, with a queue per repo to prevent multiple merges when several PRs are ready. A fail job prevents the merge.
• 🚦 skip-ci: Add [skip ci] on merge commit when merge is done with autoMerge.
• ♻️ Automatically delete the branch after this PR is merged. (⚠️ Legacy Option: Delete branch with Github Setting)

Actions:

• 🐛 Force updating reviewflow checks for this PR. Use this to try to fix reviewflow checks that are still missing/pending, which might happen if webhook failed or something bad happened when reviewflow tried to send the status check to github.
• 🔄 update branch: Merge base branch in this PR's branch. Only works if merging is possible without conflicts.

[manoraj]

Similar issue for the latest tag. Though yarn dedupes correctly when the latest tag matches with the resolved version, deduping with this tool will create the separate entry in the lock file