Allow for dynamic loading of dependencies not specified in files array

[lastmjs]

As far as I understand it, I have to explicitly define all files in the files configuration array before they are allowed to be loaded into the browser...why is this necessary? I'm building a tool on top of karma, so I need to be able to dynamically allow tests to import all of their dependencies. Right now I cannot fetch or use ES Modules on files that are not explicitly defined in the files array, and I can imagine this becoming very cumbersome as the dependency graph of a file to test could be quite complex, visiting a variety of different paths that I might not know at build time.

[johnjbarton]

Reopen if this is not a dup of #2684

[lastmjs]

Is the ES Modules support going to allow files to be requested from Karma's server that are not explicitly listed in the files array?

[johnjbarton]

Why do you want that feature? Your original post said.... ES modules.

[lastmjs]

My original post mentions ES Modules as a means to load dependencies yes, but I also mentioned using fetch. The main point is that any dependency, no matter how it is loaded, by ES Modules or plain http requests, should be loadable without having to explicitly list the file in the files array. I'm getting around this right now by proxying everything to another development server, which works for me but I don't think should be necessary.

[johnjbarton]

Ok, I'll reopen even though I don't really agree. Explicit lists help ensure that tests are reproducible. Having a test solution which allows tests to pass if and only if the file system contains some unspecified files means the tests cannot be reproduced.