In addition - package resolutions are attempted for resolution at runtime before throwing a not found error.

Codecov Report

Merging #378 into master will decrease coverage by 1.11%.
The diff coverage is 73.07%.

@@            Coverage Diff             @@
##           master     #378      +/-   ##
==========================================
- Coverage   74.41%   73.29%   -1.12%     
==========================================
  Files          12       14       +2     
  Lines         387      397      +10     
==========================================
+ Hits          288      291       +3     
- Misses         99      106       +7

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b5033ed...698583c. Read the comment docs.

This change also allows us to remove the entire code path around the custom externals function we have, which is currently double-resolving all package resolutions (and incurring the statting and performance costs of that). I haven't removed it here because the externals warning is a feature we need to consider if we want to remove, but I would personally be quite happy removing those logs too.

If these warnings are decreasing performance, we should remove them.

Like you mentioned before: if the module require is tried at runtime and not found, then there will be an error instead. I think this error is pretty self-explanatory.

Error: Cannot find module 'unknown'

Can all those issues be closed now?

Yes, all those issues can be closed!