Closed
Description
Posting here to see if others are having this issue and if it's one with the configuration Webpacker creates.
I had this working with many previous versions of the wonderful JavaScript toolchain, but now with the latest of everything, I get
Error: EACCES: permission denied, mkdir '/_karma_webpack_'
The source for karma-webpack seems to be totally wrong, but it's been like that for 10+ months, so I think there's a subtly I'm not aware of.
I'm using the latest Webpacker-generated configuration files, with zero changes.
My devDependencies are:
"devDependencies": {
"jasmine": "^2.6.0",
"jasmine-core": "^2.6.2",
"karma": "^1.7.0",
"karma-jasmine": "^1.1.0",
"karma-phantomjs-launcher": "^1.0.4",
"karma-webpack": "^2.0.3",
"testdouble": "^2.1.2"
}
My karma.conf.js
looks like:
module.exports = function(config) {
config.set({
frameworks: ['jasmine'],
files: [
'**/*.spec.js'
],
preprocessors: {
'**/*.spec.js': [ 'webpack' ]
},
webpack: require('../../config/webpack/test.js'),
browsers: ['PhantomJS'] })
}
If I sudo mkdir /_karma_webpack_ && sudo chmod 777 /_karma_webpack
everything works. This is not a great solution, but i have no idea how to change it or why it's now broken.
Anyone have any ideas?
Metadata
Metadata
Assignees
Labels
No labels