Handling large number of imports/dependencies, and the waterfall problem

[MilanKovacic]

Hi, this is more of a discussion than an issue, on how to handle projects with large import maps.
Here is an import map representative of a very small project:

https://generator.jspm.io/#NY0xDoAgEASp+IklFyEE7eQTPoDgFSQCBo7C30sU29md3Ykzxrc9UaATD1bQeRJHjlauoGAeICQ6rQENeoCSG2F5iwakBvXx36oYXZ/0ogXxBQpklyvd/UX4HK+cMFHt9gzLA+/6AtmFAA

The import map only has 6 imports. Adding preloads triggers over 500 requests.
I saw the proposal regarding depcache, but what is currently the best way to handle this?
In large applications, the current approach does not seem scalable.

[guybedford]

If anything, import maps force you to see what you're loading instead of having an invisible bundle. And they don't solve dependency bloat any other way than making it apparent.

Specifically there, semantic-ui using lodash-es is the problem.