De-dupe glob resolutions before passing to webpack

[shilman]

Originally posted by @ndelangen in #3968 (comment)

Interesting @felipenmoura . So the idea is that when you have multiple globs that resolve to the same story, some race condition is triggered that blows up the startup time?

I'm hoping that in the future, we don't rely on webpack's require.context at all anymore, and we resolve the globs (and can de-dup them) in node before starting webpack.

Sounds that might resolve that issue @shilman ?

@ndelangen that it would. it might also help with #12771 ?

[ndelangen]

I don't really see a reason to think it would fix #12771 but I'm also not ruling it out.

[shilman]

Maybe we just warn about this rather than actually de-dupe?

[stale]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!