-
Notifications
You must be signed in to change notification settings - Fork 116
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
arguments to path.resolve must be strings #142
Comments
I'm not entirely clear, did this happen on 0.10.1? Because if it only happened on 0.10.0 that's fine because that release is broken. |
I checked 10.0 and 10.1 and both broke it for me. The only one that works for me is 0.9. To reproduce you can pull down that repro and do npm install and then grunt test. |
I had a similar issue due to the data.files not flattening properly. I changed the grunt-karma.js file by adding To test it pass The code now looks like. if (data.files || options.files) {
data.files = [].concat.apply(options.files || [], this.files.map(function(file) {
return file.src.map(function(src) {
var obj = {
pattern: src
};
['watched', 'served', 'included'].forEach(function(opt) {
if (opt in file) {
obj[opt] = file[opt];
}
});
return obj;
});
}));
data.files =_.flatten(data.files);
} |
Nice find!, Is there any chance we could add this to the latest release? |
I have this problem with |
fix: Flatten files array. Closes karma-runner#142
fix: Flatten files array. Closes #142
@dignifiedquire I just upgraded to 0.11.1 and I'm still getting the same error. |
If you want you can pull down my repo https://github.com/exceptionless/Exceptionless.UI (run |
Same problem here. Was trying to go from 0.8 to 0.11. A lot going on in the 'files' to get all the angular templates compiled, etc. |
Fixed in |
Thanks! I'll try and check this out soon! |
I just tried upgrading our project ( https://github.com/exceptionless/Exceptionless.UI ) from 0.9 to the latest version and I started getting errors:
I tried 10.1 and nothing but it definitely happened after .9
The text was updated successfully, but these errors were encountered: