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

TypeError with io.js v2.3.0 #1454

Closed
bricss opened this issue Jun 15, 2015 · 4 comments
Closed

TypeError with io.js v2.3.0 #1454

bricss opened this issue Jun 15, 2015 · 4 comments

Comments

@bricss
Copy link

bricss commented Jun 15, 2015

ERROR [karma]: [TypeError: options must be a string or an object]
TypeError: options must be a string or an object
    at new WriteStream (fs.js:1798:11)
    at Object.fs.createWriteStream (fs.js:1784:10)
    at c:\Users\<username>\Documents\Aptana Studio 3 Workspace\admin-gui\node_modules\karma-html-reporter\index.js:89:22
    at FSReqWrap.oncomplete (fs.js:82:15)
.write(string, encoding, offset, length) is deprecated. Use write(string[, offset[, length]][, encoding]) instead.
@dignifiedquire
Copy link
Member

Thanks, could you provide the full DEBUG log please and if possible your karma.conf?

@bricss
Copy link
Author

bricss commented Jun 15, 2015

Actually this bug related to karma-html-reporter, I've created issue in theirs repo.

It could be easily fixed by adding empty {} object in options:

writeStream = fs.createWriteStream(reportFile , {}, function(err) {
    if (err) {
        log.warn('Cannot write HTML Report\n\t' + err.message);
    } else {
        log.debug('HTML report written to "%s".', reportFile);
    }
});

But I've think its an issue with new version of io.js v2.3.0, I will rise a new bug in theirs repo too.

@dignifiedquire
Copy link
Member

Thanks. It looks like it generated quite the discussion on the iojs repo.

I will close this issue as there is nothing we can do from this side.

@ChALkeR
Copy link
Contributor

ChALkeR commented Jun 17, 2015

Just for the reference: this is not an io.js bug, it's a bug in karma-html-reporter.

It looks like the idea of placing a work-around for such errors in io.js did not receive any support, and this is not going to be fixed on the io.js side.

The proper solution would be to merge dtabuenc/karma-html-reporter#27 into karma-html-reporter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants