lockfile optimized

[bestander]

just updated lockfile that selfupdates after install

[SimenB]

Why isn't this deduped away?

I ask because my pet peeve with yarn is that doing yarn on empty node_modules or yarn --force with node_modules will dedupe it, but running yarn dedupe cheekily says that deduping is done by default.

[bestander]

Currently Yarn does deduping on the go "for free", this PR should address it #3729.

I think deduping should be either during upgrade operations or when deduping was requested with a command.
Not sure if --force should dedupe

[SimenB]

Will yarn dedupe become a thing? Right now (with v0.27.5) I'm stuck manually deduping the lockfile, which really sucks.

error The dedupe command isn't necessary. yarn install will already dedupe.

This is a lie

Not sure if --force should dedupe

I agree it shouldn't, but removing the capability without adding some other way to dedupe makes me sad

[bestander]

Sorry, @SimenB, we just had to mitigate the issue of Yarn being too eager to dedupe the packages during any installation which resulted in unexpdected behavior.

Please chime in into this issue #3778 and help out to resolve it

[SimenB]

Ah, didn't know about that issue, thanks!