Can't run nile node in macOS
See original GitHub issueHi,
I’m on macOS Big Sur, and there is some system process running at port 5000. Cause of which, nile node fails to run.
Is there a way to specify the port in nile node ?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:10 (5 by maintainers)
Top Results From Across the Web
nile setup fails · Issue #63 · OpenZeppelin/nile - GitHub
Hello team. I am trying to setup a private key alias as described in the README. but I get an error. I am...
Read more >How to Run a Node.js Application on a Mac - Webucator
To run a Node. js application on MacOS, follow these three steps. Open Terminal by pressing Command+Space to open Spotlight Search and entering...
Read more >Installing node with brew fails on Mac OS Sierra - Stack Overflow
To get around this run: brew uninstall --ignore-dependencies icu4c && brew install icu4c . This command replaces @mircealungu's 2nd command. – ...
Read more >How to install Node.js and npm on macOS - Fullstack.io
In this post, we'll be looking at three different ways to install Node.js and its package manager, Node Package Manager, on macOS.
Read more >How to run Node.js on Mac after successfully installing it with ...
Please advise me, how can I start using the installed Node.js? I have a feeling that just a small bit is missing here....
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

Okay now it works! I wasn’t running them in the same directory. Thanks!
@Yijia-Chen hey there, bear in mind that merging it doesn’t automatically makes it available since we’d have to also release a new version of nile. Until we release it, I suggest you clone the PR (or
mainwhen merged) and install it locally to use it today, now.