Recently, I am writing a command line tool
NPM link , it can work normally. However, if you save Ctrl + s and run it again, you will report an error env: node/R: no such file or directory. You need to NPM link again. Do you need to link every time you modify it
it’s strange that the target file is the same as the source file, so why can’t it be saved
Causes and Solutions
Pay attention to the character ‘R’. The parser takes the newline character as part of the path! Embarrassed
change CRLF to LF
- node env: node\r: No such file or directory
- [Solved] Expected linebreaks to be ‘LF’ but found ‘CRLF’.
- [How to Solve Error] warning: LF will be replaced by CRLF in README.md.
- On branch master nothing to commit, working tree clean ERROR: Repository not found. fatal: Could …
- Conflict between git windows and MAC newline
- Git Warning: LF will be replaced by CRLF | fatal: CRLF would be replaced by LF
- One line command / usr / bin / Perl ^ m: bad interpreter
- [git] warning: LF will be replaced by CRLF | fatal: CRLF would be replaced by LF
- Shell script error newline syntax error near unexpected token
- error: RPC failed; curl 18 transfer closed with outstanding read data remaining