Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Polling option not picked up by watchpack #55

Closed
gilbox opened this issue Jun 29, 2015 · 1 comment
Closed

Polling option not picked up by watchpack #55

gilbox opened this issue Jun 29, 2015 · 1 comment

Comments

@gilbox
Copy link

gilbox commented Jun 29, 2015

Hi, I am reposting this here even though I'm not convinced it's actually a problem with karma-webpack. This is a direct copy+paste from the issue I posted in the webpack issue tracker...


Using webpack v1.9.11, I am trying to enable poll-based watching, in my karma configuration I have

    webpack: {
        watchOptions: {
          poll: true
        },
        devtool: 'inline-source-map',
        resolve: webpackConfig.resolve,
        module: {
          loaders: [buildConfig.loaders.babel]
        }
    }

It seems as if the watchOptions options are not being propagated to watchpack. My other options work. I can add a single line to node_modules/webpack/node_modules/watchpack/lib/DirectoryWatcher.js:

     options.poll = true;

in the DirectoryWatcher function and then polling works.

Any ideas?

gilbox added a commit to gilbox/karma-webpack that referenced this issue Jul 2, 2015
To activate polling, in karma configuration you must do:

```
    webpackMiddleware: {
      watchOptions: { poll: true }
    },
```
@gilbox
Copy link
Author

gilbox commented Jul 14, 2015

still half broken. now polling works when the spec file is updated, but if i update the file that the spec is testing polling doesn't pick up the change

@gilbox gilbox closed this as completed Jul 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant