Skip to content
This repository has been archived by the owner on Feb 16, 2022. It is now read-only.

Cliflix cat't start - /usr/bin/env: - no such file error #46

Open
mpuz opened this issue Nov 27, 2021 · 2 comments · May be fixed by ElonSatoshi/cliflix#1
Open

Cliflix cat't start - /usr/bin/env: - no such file error #46

mpuz opened this issue Nov 27, 2021 · 2 comments · May be fixed by ElonSatoshi/cliflix#1

Comments

@mpuz
Copy link

mpuz commented Nov 27, 2021

Ubuntu 20.04.3 LTS
Node v14.17.2

Cliflix produces error on start -

/usr/bin/env: ‘node --no-deprecation’: No such file or directory
/usr/bin/env: use -[v]S to pass options in shebang lines

all other globally installed modules work as usual

@kirillt
Copy link

kirillt commented Dec 7, 2021

The same error.

Fedora 32
Linux lenovo 5.11.12-100.fc32.x86_64 #1 SMP Wed Apr 7 16:52:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
NPM 6.14.12
Node v12.22.1

@PACordonnier
Copy link

Hi,

I've got the same issue and fixed it.
The simple fix is to revert this commit: 9b3fd27

"On Linux, the entire string following the interpreter name is passed as a single argument to the interpreter, and this string can include white space." I don't know if that's the case on Mac. See this SO for more info https://stackoverflow.com/a/8108970/4338111

For a quick fix, just go to your npm bin directory (location depends on your distro and if you're using nvm) and remove '-- no-deprecation'

For a more in depth fix, maybe revert the commit I linked above to be more compatible with more environments.

ElonSatoshi added a commit to ElonSatoshi/cliflix that referenced this issue Jul 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants