Comment on page
Here are some solutions to frequently encountered problems.
These errors can occur, if npm was installed without the use of a version manager.
This error may happen because
PATHenvironment variable was not correctly updated to contain path to Node.js binary.
If you use Linux, ensure the following command is in your
~/.bashrcfor bash shell or
~/.zshrcfor zsh shell:
If you have installed Node.js using Homebrew on MacOS, npm binaries could be found in
/usr/local/share/npm/bin. So, in your
~/.zshrcfile add the following:
If you use Windows, add path to NodeJS bin directory via environment variables settings dialogue and relaunch console window.
This error occurs in two cases. Either the docker daemon isn't running, or current user doesn't have rights to access docker.
sudo usermod -a -G docker $USER
Make sure to restart the system or log out and back in, for the new group settings to take effect.
Getting this error means docker service is not running or missing due to incorrect Docker installation, partiularly in the case of Docker Desktop. Try reinstalling Docker and making sure the daemon is running.
If you use certain adblockers, after you have started Evernode SE the Ever Live explorer at http://127.0.0.1/landing might fail to load (you get a rotating icon and various warnings and errors in the console).
After it is done, reload terminal and install everdev via
npm i everdev -gagain.