Line Endings causing ‘node\r’: No such file or directory
See original GitHub issueHi Guys,
Thanks for writing the package!
We are trying to get this running in our teams, on various environments, but our Linux and Mac users have problems with the line endings.
$ craco build
/usr/bin/env: ‘node\r’: No such file or directory
error Command failed with exit code 127.
Is it possible to have the \r removed?
Thanks! Cam
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Line Endings causing 'node\r': No such file or directory · Issue #33 ...
Hi Guys, Thanks for writing the package! We are trying to get this running in our teams, on various environments, but our Linux...
Read more >env: bash\r: No such file or directory - windows - Stack Overflow
The error message suggests that the script you're invoking has embedded \r characters, which in turn suggests that it has Windows-style \r\n line...
Read more >env: node\r: No such file or directory
This problem happens mostly in the Mac/Linux operating system if the node tries to execute a js file having windows-style line endings. The...
Read more >Fixing "env: node : No such file or directory" on mac for an ...
If you install an npm package using yarn and you get this error it means that the package author is using windows line...
Read more >Fix NPM No Such File Error on WSL2 - PäksTech
I was working on a Node.js project and decided to run it on top of Windows Subsystem for Linux but it just wouldn't...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Works fine with 3.0.0, thx @patricklafrance !
It should be fix with 3.0.0 alpha
@cammanderson @abenhamdine can you test it please?