How do you split into external bundles? about karma-browserify HOT 8 CLOSED

You'd have to supply that yourself since there isn't a way to make prebundle async. The ideal way to do it is to drop the Karma CLI entirely and compose a gulp task (karma-as-promised should be helpful there). Generate the external bundle there, perhaps even to a tmp folder, and then load it in your Karma files array.

from karma-browserify.

Ah, so multiple builds, each with its own set of files, is not really from within karma. Instead I would just do:

        files : [
          'test/unit/**/*Spec.js',
            'app/dist/vendor.js'
        ],
        preprocessors: {
            'test/unit/**/*Spec.js' : ['browserify']
        },

and build my app/dist/vendor.js (or whatever other path I want) as part of a separate gulp/grunt/npm task. Since it changes so infrequently, updating that one manually (without watchify) is not the end of the world... and gulp.watch could probably watch it for me anyways?

from karma-browserify.

It would be cool if Karma had an async interface for adding files, but unfortunately it doesn't. That essentially means that all the files need to exist before Karma runs. By the way, I use browserify-shim to use Angular as a window global with a plain old concatenated vendor file. Makes it a whole lot easier since you can just add your vendor files directly to the Karma files array.

from karma-browserify.

Yeah, I used to have my own "angular-cjs.js" and "jquery-cjs.js" files to shim, but now I use browserify-shim. Much easier.

I do like browserify, but in an angular world, you almost wish the two were merged, so it could read the angular modules and find the relevant files.

I will close this out. Thanks for the assistance.

from karma-browserify.

Well Angular modules don't actually specify file structure relations like CommonJS, nor are they intended to. Angular's modules are design for dependency injection and have no opinion about how they load them. That said, I'm with you that it's a mess. Angular is supposed to ship with CommonJS support on npm in 1.3. Then there will be a transition process where everyone who wrote their modules to expect window.angular has to go fix them. I generally find the average quality of popular (50+ stars) Angular modules to be extremely low. The best way to prepare is to write everything with browserify-shim. Then it's a one line fix to your package when Angular can be required.

from karma-browserify.

I haven't delved too deeply into most of the modules, but I have seen a lot of junk.

Yeah, I like the cleanliness of it. The less I have to do inside individual files for maintenance, the better.

Is it supposed to finally ship with npm support? I would very much like to do npm install angular and be done with it. Then I can require('angular') or maybe require('angular/angular-resource') natively.

from karma-browserify.

Yes: angular/angular.js#2877

You +1'd it 3 days ago! 😄

Slated for rc5 which I'm guessing will land in 2 weeks.

from karma-browserify.

I know I +1'd it... but I didn't realize they had agreed.

Oh, now I see the "added to 1.3.0 milestone". That will be nice.

from karma-browserify.