module not found when running tests on windows about karma-browserify HOT 3 CLOSED

This problem can be circumvented by excluding the source files in the files and preprocessors section (they are pulled in / bundled via browserify anyway).

By changing the configuration to

        files : [
            'src/**/*.spec.js'
        ],

        preprocessors : {
            'src/**/*.spec.js' : [ 'browserify' ]
        },

the example works on my machine. It should work for you, too.

I still need to dig a bit deeper into why that is actually causing problems when the source files are included.

from karma-browserify.

See #50 for more examples of issues caused by including source

from karma-browserify.

I have opened #52 to fix that behavior. To be bullet-prove we should not fail if users actually included the sources.

from karma-browserify.