-
Notifications
You must be signed in to change notification settings - Fork 10
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
webpack preprocessor not running #28
Comments
Thanks, reproduced. Caused by current working directory specified when running karma process. |
Tried to create module.exports = require('./test/karma-idea.config'); And it fails in Terminal when running as |
I changed the js file to:
|
Seems to work like that! Maybe this is just adding that to the docs 😄 |
Thanks so much for the help on this! |
Great! It works for me too. However, I'm still in the dark why this doesn't work, require('babel-register');
module.exports = require('./test/karma-coverage.config.babel'); |
I think b/c webpack gets confused about which directory it's in. |
I got the same problem using browserify instead of webpack, thus the workaround doesn't work for me. Any ideas on how to make karma use the configured "base" as work directory for running single specs? |
@Macavity Not sure I understand your problem fully. Could you please provide mode details about it in a separate issue? |
Sure, will do. |
I've got my tests setup w/ webpack and coverage preprocessors. These work as expected via CLI, but when I try to run via karma-intellij I get the following error (which makes me think the preprocessor isn't running):
Here's the config file I'm trying to use:
https://github.com/krux/prescribe/blob/jnewman-repro-intellij-integration-issue/test/karma-idea.config.js
Any pointers would be helpful. I've got a similar setup w/ coffee script preprocessors that works exactly as planned, so I'm wondering if it's something specific about multiple preprocessors.
For reference, I've attached images of my setup:
IntelliJ details:
The text was updated successfully, but these errors were encountered: