lodash.debounce for laterLogMissingDependencies delays process exit by 1 second about babel-polyfills

[nicolo-ribaudo]

Defaulting to per-file will produce an enormous output for some polyfills like es-shims, but I can:

• Reduce the delay from 1s to maybe 100ms
• Remove the delay for core-js, where it's mostly not needed.
• Only delay if there is actually a missing dependency to log.

[ljharb]

Can you elaborate more on per-file and why its impact varies by polyfill provider?

[nicolo-ribaudo]

When there is a missing dependency, this package logs about it.
We collect all the missing polyfills, and then log something like

Please run
  npm install polyfill-a polyfill-b polyfill-c polyfill-d

If we'd do that per-file, we cannot create a single command to copy-paste. It would look more like

Please run
  npm install polyfill-a polyfill-b
Please run
  npm install polyfill-c
Please run
  npm install polyfill-d

Where every log comes from a different file. core-js is a single package so it logs almost once, but for es-shims (which is a collection of a lot of different packages), it can log a very long list of commands to run (in the worst case, max(number of files, number of polyfills)).

[ljharb]

gotcha. i guess i'm not sure why this needs to be debounced here instead of just ran once after everything's finished?

[nicolo-ribaudo]

Because Babel plugins don't have the concept of "after compiling the project" but only "in this file" (this might change in the future, but not soon).

[ljharb]

ah, that's a painful limitation :-/