“No such file or directory” when running node script [duplicate]
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
This question already has an answer here:
“Can't cd to /home/user” when sourcing a script [duplicate]
4 answers
/usr/bin/env: ‘noder’: No such file or directory
I keep receiving this output when i try to run something. Any ideas on how to fix this?
command-line node.js
New contributor
marked as duplicate by Jeff Schaller, sebasth, G-Man, mosvy, elbarna 3 hours ago
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
up vote
0
down vote
favorite
This question already has an answer here:
“Can't cd to /home/user” when sourcing a script [duplicate]
4 answers
/usr/bin/env: ‘noder’: No such file or directory
I keep receiving this output when i try to run something. Any ideas on how to fix this?
command-line node.js
New contributor
marked as duplicate by Jeff Schaller, sebasth, G-Man, mosvy, elbarna 3 hours ago
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
the proposed duplicate also links to unix.stackexchange.com/q/189254/117549
– Jeff Schaller
7 hours ago
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
This question already has an answer here:
“Can't cd to /home/user” when sourcing a script [duplicate]
4 answers
/usr/bin/env: ‘noder’: No such file or directory
I keep receiving this output when i try to run something. Any ideas on how to fix this?
command-line node.js
New contributor
This question already has an answer here:
“Can't cd to /home/user” when sourcing a script [duplicate]
4 answers
/usr/bin/env: ‘noder’: No such file or directory
I keep receiving this output when i try to run something. Any ideas on how to fix this?
This question already has an answer here:
“Can't cd to /home/user” when sourcing a script [duplicate]
4 answers
command-line node.js
command-line node.js
New contributor
New contributor
edited 7 hours ago
Kusalananda
114k15218349
114k15218349
New contributor
asked 7 hours ago
Andrew Barrios
32
32
New contributor
New contributor
marked as duplicate by Jeff Schaller, sebasth, G-Man, mosvy, elbarna 3 hours ago
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by Jeff Schaller, sebasth, G-Man, mosvy, elbarna 3 hours ago
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
the proposed duplicate also links to unix.stackexchange.com/q/189254/117549
– Jeff Schaller
7 hours ago
add a comment |
the proposed duplicate also links to unix.stackexchange.com/q/189254/117549
– Jeff Schaller
7 hours ago
the proposed duplicate also links to unix.stackexchange.com/q/189254/117549
– Jeff Schaller
7 hours ago
the proposed duplicate also links to unix.stackexchange.com/q/189254/117549
– Jeff Schaller
7 hours ago
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Whatever script you are running has, as its first line,
#!/usr/bin/env node
The only issue with this is that it's also a DOS text file. This is evident from the r
in the error message. r
is a common way to encode a carriage return character, and DOS text files have these at the end of each line, before the linefeed character that serves as "newline" on Unix systems.
Convert the script file to a Unix text file using e.g. the dos2unix
utility.
This was it. Thank you.
– Andrew Barrios
7 hours ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Whatever script you are running has, as its first line,
#!/usr/bin/env node
The only issue with this is that it's also a DOS text file. This is evident from the r
in the error message. r
is a common way to encode a carriage return character, and DOS text files have these at the end of each line, before the linefeed character that serves as "newline" on Unix systems.
Convert the script file to a Unix text file using e.g. the dos2unix
utility.
This was it. Thank you.
– Andrew Barrios
7 hours ago
add a comment |
up vote
1
down vote
accepted
Whatever script you are running has, as its first line,
#!/usr/bin/env node
The only issue with this is that it's also a DOS text file. This is evident from the r
in the error message. r
is a common way to encode a carriage return character, and DOS text files have these at the end of each line, before the linefeed character that serves as "newline" on Unix systems.
Convert the script file to a Unix text file using e.g. the dos2unix
utility.
This was it. Thank you.
– Andrew Barrios
7 hours ago
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Whatever script you are running has, as its first line,
#!/usr/bin/env node
The only issue with this is that it's also a DOS text file. This is evident from the r
in the error message. r
is a common way to encode a carriage return character, and DOS text files have these at the end of each line, before the linefeed character that serves as "newline" on Unix systems.
Convert the script file to a Unix text file using e.g. the dos2unix
utility.
Whatever script you are running has, as its first line,
#!/usr/bin/env node
The only issue with this is that it's also a DOS text file. This is evident from the r
in the error message. r
is a common way to encode a carriage return character, and DOS text files have these at the end of each line, before the linefeed character that serves as "newline" on Unix systems.
Convert the script file to a Unix text file using e.g. the dos2unix
utility.
answered 7 hours ago
Kusalananda
114k15218349
114k15218349
This was it. Thank you.
– Andrew Barrios
7 hours ago
add a comment |
This was it. Thank you.
– Andrew Barrios
7 hours ago
This was it. Thank you.
– Andrew Barrios
7 hours ago
This was it. Thank you.
– Andrew Barrios
7 hours ago
add a comment |
the proposed duplicate also links to unix.stackexchange.com/q/189254/117549
– Jeff Schaller
7 hours ago