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
martin@laptop:~/src/typedoctest$ typedoc --out doc/ --module commonjs test.ts
: No such file or directory
martin@laptop:~/src/typedoctest$
The error message is not so helpful, but it seems this is caused by the script having Windows line endings, which confuses the Linux shell that tries to parse the "#!/usr/bin/env node" line.
See also e.g. npm/npm#4607 who struggled with the same problem. Don't know what the best solution would be in this case, as you probably have the file checked out on Windows with automatic LF <-> CRLF translation?
The file isn't auto-generated, is it? In that case, it might help marking it as binary for git, and 'manually' convert the line-endings to LF (just on that file).
I converted it in my ~/npm/bin folder for testing, and that indeed seems to work.
The text was updated successfully, but these errors were encountered:
You are right, thanks for pointing out the solution. I've converted the line endings in the entire project and tested it on a Mac. The binary seems to work right now, version 0.0.4 contains the updated files. Can you confirm it for the linux platform?
When I run the commandline tool on Linux, I get:
The error message is not so helpful, but it seems this is caused by the script having Windows line endings, which confuses the Linux shell that tries to parse the "#!/usr/bin/env node" line.
See also e.g. npm/npm#4607 who struggled with the same problem. Don't know what the best solution would be in this case, as you probably have the file checked out on Windows with automatic LF <-> CRLF translation?
The file isn't auto-generated, is it? In that case, it might help marking it as binary for git, and 'manually' convert the line-endings to LF (just on that file).
I converted it in my ~/npm/bin folder for testing, and that indeed seems to work.
The text was updated successfully, but these errors were encountered: