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
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:
Activity
pod4g commentedon Jun 5, 2018
Hi, May be you should run
sudo ln -s /usr/bin/nodejs /usr/bin/nodesendrecv commentedon Jun 5, 2018
I think it must be something else. That command returns an error because
/usr/bin/nodealready exists. I currently have node installed with both pacman (because it's a dependency of some locally installed apps like atom) and withnvm, so when I runwhich nodeit returns:/home/sendrecv/.nvm/versions/node/v10.3.0/bin/nodepod4g commentedon Jun 5, 2018
Try
which envandtype /usr/bin/env. Then run/usr/bin/env node.danner26 commentedon Jun 5, 2018
Same issue here, node 10. The env is set properly (I think) and both
/usr/bin/envand/usr/bin/env nodework by themselves, but not when running hiperpseudolog commentedon Jun 6, 2018
Hi, was just gonna report that myself. The problem lies within your shebang.
hiper/src/index.js
Line 1 in aa30b16
Linux (unlike BSD it seems) doesn't support more than one argument to the shebang command. (Details)
Get rid of the
--no-warningsargument and it should function properly. node added support for aNODE_NO_WARNINGSenvironment variable. Maybe use that as a workaround?danner26 commentedon Jun 6, 2018
@pseudolog has it right, remove the
--no-warningsand it will work correctlyand I agree with the
NODE_NO_WARNINGSenv variable as a work around, I think that would be the best course of actionpod4g commentedon Jun 6, 2018
@pseudolog Well done!!!!
pod4g commentedon Jun 6, 2018
Hi guys.
I change the code of hiper/src/index.js as follow. The warning message will still appear
Can someone help me?
zhiyan commentedon Jun 7, 2018
Maybe add a shell wrapper, instead of excute the index.js directly.
pseudolog commentedon Jun 7, 2018
I guess the cleanest solution would be to actually handle those promise rejections. Otherwise there's
process.removeAllListeners('warning')pod4g commentedon Jun 8, 2018
@zhiyan Please give me more details. what should i do？
Fixes pod4g#20, pod4g#5
Fixes pod4g#20, pod4g#5
Merge pull request #21 from zhiyan/master
pod4g commentedon Jun 8, 2018
The problem has been solved, please upgrade hiper to
0.0.15run below to upgrade:
thr pr: #21