Safari caches old bundles about karma-browserify HOT 7 CLOSED

karma-browserifast uses a similar strategy (a tmp file) so it's helpful to hear that it's working. karma-bro uses watchify to do incremental bundles rather than trying to implement a separate watcher with chokidar. I don't think it's possible to change the filename without breaking Karma's handling of file matching. Mind whipping up a quick repo with your config so we can try to reproduce this?

from karma-browserify.

Unfortunately, it's all proprietary for the moment, so I can't share much of it. If I find some time in the next few days, I'll see if I can simulate a fake project.

Would simply adding a cache busting parameter (e.g. ?cachebust=<Date.now()>) also break the karma file matching?

Here's the karma config:

module.exports = (config) ->
  config.set
    frameworks: [
      'mocha'
      'browserify'
    ]

    basePath: '.'

    files: [
      'test/unit/spec/**/*.js'
      'test/integration/spec/**/*.js'
    ]

    exclude: [
      # skip the shim files, shim config in package.json will load them
      'test/unit/spec/**/*.shim.js'
      'test/integration/spec/**/*.shim.js'
    ]

    preprocessors:
      'test/unit/spec/**/*.js': ['browserify']
      'test/integration/spec/**/*.js': ['browserify']

    hostname: '127.0.0.1'

    port: 8000

    reporters: [
      'mocha'
    ]

    browserify:
      debug: true
      watch: true
      transform: [
        'browserify-shim'
      ]

    browserNoActivityTimeout: 5*60*1000
    browsers: [
      # 'ChromeWithoutSecurity'
      'Chrome'
      'Firefox'
      'Safari'
    ]

    browserNoActivityTimeout: 5*60*1000

    customLaunchers:
      ChromeWithoutSecurity:
        base: 'Chrome'
        flags: ['--disable-web-security']

from karma-browserify.

My understanding is that Karma is responsible for reloading and filenames can't be changed

from karma-browserify.

Yes, karma is 100% in charge of caching files (and appending cache busting parameters, if needed).

Try using chrome and report if the problem persists. If so, it might be a problem with the karma-safari-launcher.

I experienced some caching problems with IE and PhantomJS, too but there is nothing karma-bro can do to mitigate this.

from karma-browserify.

Feel free to reopen the issue if you have a reproducible test case.

from karma-browserify.

I get this all the time running karma interactively (ie: not using a launcher).

from karma-browserify.

Which environment / karma / karma-bro version do you use?

from karma-browserify.