Automatically generate PackageExtensions entries?

[MrChrisRodriguez]

I've been trying to add PackageExtensions entries to suppress errors with very little luck (i.e. warnings still appear) which has been frustrating and led me to wonder:

Why isn't Yarn recommending PackageExtension entries to me?

Yarn appears to understand:

• which modules are trying to use dependencies they're not explicitly listing
• on my system, which versions of those unlisted dependencies are available and being used

Couldn't this information be combined to make a starting-point PackageExtension recommendation? Even if Yarn is overzealous, can make the occasional mistake, and won't know the entire supported range, this would be a boon for developers trying to resolve these problems.

I also imagine this could accelerate the pace with which developers explicitly add dependencies to the libraries they use, too.