Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Can't execute cli when global
See original GitHub issueHi,
When installing globally and called from an OS X terminal, i got this error message :
/usr/local/bin/mycli: line 1: syntax error near unexpected token(’
/usr/local/bin/mycli: line 1: const vorpal = require('vorpal')();'
Do i’m missing something ?
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Can't run "npm install expo-cli --global" - Stack Overflow
Open Windows PowerShell as administrator and run npm install expo-cli --global --no-optional command. Share.
Read more >Troubleshooting AWS CLI errors - AWS Command Line Interface
Diagnose and fix common AWS Command Line Interface (AWS CLI) errors. ... Here's an example of a command run with and without the...
Read more >Troubleshoot .NET tool usage issues - Microsoft Learn
If you're trying to run a global tool, check that the PATH environment variable on your machine contains the path where you installed...
Read more >How to fix a "Command not found" error in Linux - Red Hat
Global variables come predefined in your login shell, but they aren't immutable and can be modified or deleted according to your preferences.
Read more >Execute commands and run tools in Terminal on Mac
Execute commands in the shell. In the Terminal app on your Mac, enter the complete pathname of the tool's executable file, followed by...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I found the issue 💃
You need to include this at the top of your file:
#!/usr/bin/env nodeOoooh ! Perfect ! It’s working. 👍
Thx for the help 😉