Open wojtekmaj opened 1 year ago
This is a known issue due to the working mechanics or yarn.lock
. yarn.lock
lists all dependencies at the top level.
What do you think about just scanning it twice? Scan - add resolutions - install - scan - remove redundant resolutions? Or at least, make the install command remove redundant packages so that we could manually do just that?
I have a fairly standard React app. Here are all the deps:
This is the result of
yarn dlx nolyfill install
in my repository:upon carefully reviewing the list, I've noted that many of the packages are not used at all - not anymore, because nolyfill removed the need for them. The final list, resulting with the same lockfile, was: