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

No output produced on Windows with node-v0.12.0 #77

Closed
samuelbjohnson opened this issue Mar 2, 2015 · 1 comment
Closed

No output produced on Windows with node-v0.12.0 #77

samuelbjohnson opened this issue Mar 2, 2015 · 1 comment

Comments

@samuelbjohnson
Copy link
Contributor

When I run RetireJS in a Windows environment, I'm no longer seeing any output. I know it runs to completion, because if I use the --outputformat json option, I see an empty json array.

The problem seems to occur with node-v0.12.0 on Windows (though not on Mac or Linux), and it doesn't occur with node-v0.10.36 (the previous stable version). I can also duplicate the problem with versions of 0.11 greater than or equal to v0.11.7.

@eoftedal
Copy link
Contributor

eoftedal commented Mar 3, 2015

I think this is related to UTF-8. The § in §§version§§ is UTF-8 encoded in the lib/retire.js file, but without a BOM in the beginning of the file, windows seems to interpret it as ascii. I'm not sure, appart from adding a BOM, if there is a way to instruct windows to interpret the files as UTF-8.

At least that seems to be what's going on in the Chrome plugin on windows... allthough that might actually be chrome...

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

No branches or pull requests

2 participants