You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2020. It is now read-only.
Yes. IMO, that is still on the table. It does allow split bundles, however, from what I can tell, the split needs to be defined up front. We can't just bundle AVA once, then add additional bundles dynamically that exclude everything in the first bundle. I haven't explored deeply enough to confirm, but I think that is the case.
Ideally AVA would have mechanisms for browser testing across a range of bundlers.
Browserifies
b.external(ext)
method suffers from a few issues whenext
is another bundle.b2.external(b1)
before you callb1.bundle
(Demonstrate bug with external bundles that are already complete browserify/browserify#1577). This makes it pretty useless for bundle splitting forkarma-ava
. The idea is to bundleava
once as an external to avoid the expense of bundling it for every single test.lib/externalize-bundle.js
pulls it's implementation directly from the browserify source. It solves1
, but2
remains an issue.The text was updated successfully, but these errors were encountered: