Closed matt-allan closed 4 years ago
I can confirm this problem with ubuntu 18.04 and node v8.10
I've been reading up on this and it sounds like if you check the project out with git the line endings should be fixed automatically.
The problem seems to happen when you check the project out on a windows computer, then publish to NPM, as explained in this NPM issue.
I think we might be able to set npm/cli.js text eol=lf
in a .gitattributes
file to prevent this from happening? It would ensure that the line endings are always converted to LF
on checkout, even on Windows. We would then need to publish a new package. I don't have a Windows machine to test this on and confirm it doesn't break anything though.
Same on Mac os with version 0.1.0
Hello,
I was following the guide in the README on Ubuntu Linux 19.04. When I tried to run
yarn start
I encountered the following error:If I execute
/usr/bin/env node
directly it works as expected:Eventually I was able to resolve the issue by running
dos2unix
on thecli.js
file:The
file
command shows thatcli.js
(and it looks like the rest of the files too) has CRLF line terminators: