-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
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
/usr/bin/env: ‘node\r’: No such file or directory #2
Comments
yep I'm on windows, I'll try using it with WSL to produce the issue and think of a solution |
I have worked around this problem just by editing my
I can close it by sending an interrupt, but nothing is generated. |
yeah so that means that you've run the package yourself and It wasn't invoked by prisma. |
only the files will be generated when prisma is the one running the generator |
Interesting. Will try that. |
sadly I don't have access to ubuntu rn, can you please try that.
then use this provider = "node_modules/prisma-typegraphql-types-generator" |
give me 10-15 minutes |
cause I think the problem is caused due to running the package from npx and the unix format. |
I am not sure why do you want me to test it again using "@latest". Latest version on NPM is still 1.0.10 which is the one I am using. |
yeah the solution is not with testing with the latest version, It's with depending on installed package in node_modules instead of loading it from npx. |
I have tried that, I get:
|
did you tried with sudo cause It's telling "Permission denied" |
No, it's not a good practice to invoke npm scripts with sudo. |
but then why the error is pointing to "Permission denied"? |
oh yeah yeah yeah sorry |
I forgot the "node" before it, that's reasonable why it's telling you that.
|
did that work? |
yes that works. TIL that typescript outputs line ending depending on the system where you run it. I would prefer |
I have opened a PR, because that |
merged you PR, Is it working properly now?
and If it's working, Is it working with npx or with using invoking the package with node from node_modules workaround. |
It's working just fine as it was before on Windows, hope using LF line endings solved the issue on unix based systems. |
tested with |
I am getting
when I try to run on ubuntu.
Are you developing on windows? Seems like this is a line ending issue like here:
docsifyjs/docsify-cli#78
maybe adding a
.editorconfig
could fix this.The text was updated successfully, but these errors were encountered: