-
Notifications
You must be signed in to change notification settings - Fork 220
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
Unhandled rejection Error: not a directory #173
Comments
#149 also if that doesn't solve your issue link your karmaConfig |
I should mention this exact config works fine if i dont have multiple entry points karma.conf
|
@th3fallen were you able to find a resolution, i have the exact problem myself. |
@alphapilgrim i was, my solution was to use jest instead 🙈 |
FWIW, I had this same error and fixed it by deleting my karma.conf.js var webpackConfig = require('./webpack.config')('test');
delete webpackConfig.entry;
module.exports = function(config) {
config.set({
// ...
webpack: webpackConfig
})
} |
Closing as this is on an older version of karma-webpack that will not receive updates, if you are having the same issues with a current build, open another ticket and I'll assist as best I can! |
If this is indeed a support request please let me know and i'll move it. i belive it to be a bug however.
I'm submitting a bug report
Webpack version:
1.13.1
Webpack Karma version:
1.8.0
Karma version:
1.2.0
Please tell us about your environment:
OSX 10.12 beta 16A313a
Browser: Phantom
Current behavior:
when running tests i get the following failure:
Unhandled rejection Error: not a directory
full error with logging of current and path
this has only started after i began splitting app: and vendor: entry points
Expected/desired behavior:
should build and test correctly
webpack.config.js
test.js
The text was updated successfully, but these errors were encountered: