We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In the published v1.0.21 NPM package, tsproto will not execute on a Linux machine.
tsproto
The output is:
/usr/bin/env: ‘node\r’: No such file or directory
The extra \r is present in the published v1.0.21 NPM package:
\r
$ hexdump -C v1.0.21/package/bin/cli 00000000 23 21 20 2f 75 73 72 2f 62 69 6e 2f 65 6e 76 20 |#! /usr/bin/env | 00000010 6e 6f 64 65 0d 0a 0d 0a 72 65 71 75 69 72 65 28 |node....require(| 00000020 27 2e 2e 2f 64 69 73 74 2f 63 6c 69 27 29 3b 0d |'../dist/cli');.| 00000030 0a |.| 00000031
To compare, here is the working version v1.0.20:
$ hexdump -C v1.0.20/package/bin/cli 00000000 23 21 20 2f 75 73 72 2f 62 69 6e 2f 65 6e 76 20 |#! /usr/bin/env | 00000010 6e 6f 64 65 0a 0a 72 65 71 75 69 72 65 28 27 2e |node..require('.| 00000020 2e 2f 64 69 73 74 2f 63 6c 69 27 29 3b 0a |./dist/cli');.| 0000002e
I don't see anything in the repo that would have caused this, so I'm suspecting it happened during the NPM package publishing process.
Thanks!
The text was updated successfully, but these errors were encountered:
still has a problem.
Sorry, something went wrong.
npm install -g nestjs-proto-gen-ts
I had the same problem I installed the package globally and solved it urgently.
No branches or pull requests
In the published v1.0.21 NPM package,
tsproto
will not execute on a Linux machine.The output is:
The extra
\r
is present in the published v1.0.21 NPM package:To compare, here is the working version v1.0.20:
I don't see anything in the repo that would have caused this, so I'm suspecting it happened during the NPM package publishing process.
Thanks!
The text was updated successfully, but these errors were encountered: