You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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...
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.
The text was updated successfully, but these errors were encountered: