-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
errors with "Command not found" on OSX, Ubuntu #319
Comments
I'm experiencing the same on Ubuntu (using vagrant with Windows host and Ubuntu guest). I suspected node-gyp to be the problem, because of several error messages I received earlier. However, thanks to #302, which was merged tonight, socket.io was replaced. socket.io required node-gyp. So this shouldn't be a problem any longer. Uninstalling and reinstalling everything (including the newest version of webpack-dev-server) still results in Any ideas how to fix this? |
I was able to solve this problem on my machine. It appears to have been an issue with permissions. I installed webpack and webpack-dev-server globally. However, even then, The problem was that npm installed the global packages to In order to avoid having to use root permissions, I changed the directory in which global packages are to be installed to a directory in I installed webpack and webpack-dev-server globally again (this time without sudo) and verified that they have been installed in my new directory. Now, I can finally run I hope this helps @tconroy! |
thanks man! |
Thanks for sharing your findings @flindenberg! I'll try this when I get home tonight. |
You're welcome! Good luck :-) |
I had the same issue using nvm on ubuntu. Just in case anyone else runs into this.
Replace the content in brackets with your specific path info for user and node version. |
thanks man! @flindenberg |
Thanks man ! It helped |
Bro, Thank youuu 👍 |
Hey there,
Not sure what's up since I've run
webpack-dev-server
in the past just fine, but currently when I try and invoke it ( either globally or locally in a project ), I'm getting the following shell error:I've tried:
A) uninstalling ( both locally and globally )
B) clearing NPM cache
C) re-installing ( both locally and globally )
but still receive the same error.
Further, I posted this originally as a question on StackOverflow, to which another user replied that they were encountering the exact same issue on Ubuntu.
Was a broken update recently pushed?
The text was updated successfully, but these errors were encountered: