"No such file" error

[sendrecv]

After npm install hiper -g, hiper baidu.com throws this exception:

/usr/bin/env: 'node --no-warnings': No such file or directory

I'm currently running Node 10 with nvm on Manjaro (Arch) Linux.

[pod4g]

Hi, May be you should run sudo ln -s /usr/bin/nodejs /usr/bin/node

[sendrecv]

I think it must be something else. That command returns an error because /usr/bin/node already exists. I currently have node installed with both pacman (because it's a dependency of some locally installed apps like atom) and with nvm, so when I run which node it returns:

/home/sendrecv/.nvm/versions/node/v10.3.0/bin/node

[pod4g]

Try which env and type /usr/bin/env. Then run /usr/bin/env node.

[danner26]

Same issue here, node 10. The env is set properly (I think) and both /usr/bin/env and /usr/bin/env node work by themselves, but not when running hiper

[pseudolog]

Hi, was just gonna report that myself. The problem lies within your shebang.

hiper/src/index.js

Line 1 in aa30b16

#! /usr/bin/env node --no-warnings

Linux (unlike BSD it seems) doesn't support more than one argument to the shebang command. (Details)

Get rid of the --no-warnings argument and it should function properly. node added support for a NODE_NO_WARNINGS environment variable. Maybe use that as a workaround?

[danner26]

@pseudolog has it right, remove the --no-warnings and it will work correctly

and I agree with the NODE_NO_WARNINGS env variable as a work around, I think that would be the best course of action

[pod4g]

@pseudolog Well done!!!!

[pod4g]

Hi guys.

I change the code of hiper/src/index.js as follow. The warning message will still appear

#! /usr/bin/env node
process.env.NODE_NO_WARNINGS = 1

Can someone help me?

[zhiyan]

Maybe add a shell wrapper, instead of excute the index.js directly.

[pseudolog]

I guess the cleanest solution would be to actually handle those promise rejections. Otherwise there's process.removeAllListeners('warning')

[pod4g]

@zhiyan Please give me more details. what should i do？

[pod4g]

The problem has been solved, please upgrade hiper to 0.0.15

run below to upgrade:

npm i hiper -g

thr pr: #21