I successfully installed localtunnel/server on an Ubuntu 18.04 VPS through ssh.
When I typed bin/server to start the server, this message came out: /usr/bin/env: ‘node -r esm’: No such file or directory
How to fix it?
I successfully installed localtunnel/server on an Ubuntu 18.04 VPS through ssh.
When I typed `bin/server` to start the server, this message came out:
`/usr/bin/env: ‘node -r esm’: No such file or directory`
How to fix it?
Seems like running node -r esm ./bin/server instead of npm run start works for a few cases.
This matter has been discussed here: https://github.com/localtunnel/server/issues/90
Seems like running `node -r esm ./bin/server` instead of `npm run start` works for a few cases.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I successfully installed localtunnel/server on an Ubuntu 18.04 VPS through ssh.
When I typed
bin/serverto start the server, this message came out:/usr/bin/env: ‘node -r esm’: No such file or directoryHow to fix it?
Same here. Spent some time trying to troubleshoot but no dice.
This matter has been discussed here: https://github.com/localtunnel/server/issues/90
Seems like running
node -r esm ./bin/serverinstead ofnpm run startworks for a few cases.Try using Node 10 instead of later versions and it should work.
Fixed this issue here https://github.com/StyleT/mytunnel-server It now runs on latest Node.js LTS via
npm start.