I know that theres a latest version on github (websocket.js) by the same author, but I specifically need a version that works with discord.js. I tried installing a usable version, with
npm install uws#10.148.1
but it doesn't work, it returns this error:
npm ERR! ELOOP: too many symbolic links encountered
I'm also not too sure which versions I should install, as I just started using discord.js.
My questions:
Firstly,
Is there a uws version compatible with discord.js that I can install, and how could I install it?
And if not:
Is there a way to fix this eloop error?
Any help would be appreciated? If I'm not clear, please drop a comment below and I'll try to clarify. Once again, thanks for any help!
I will refer you to these other posts for some detailed information on the subject.
This one involves the error you're referring to so it might be an answer to your problem.
ELOOP Error
This one involves some good information on how to use npm in different ways that may be useful.
npm outdated
I looked up the package and created a test folder to see if I could install the package you're talking about in there using npm i outdated uws#10.148.1.
I then uninstalled it using npm uninstall outdated uws#10.148.1
Everything seemed to work fine besides all the deprication errors and warnings.
Related
I hope you are doing well!
I got asked about why should I use -f to force npm install packages to install. In the documentation it states that
force npm to fetch remote resources even if a local copy exists on disk.
But does this mean that it redownloads global packages for the local project or what does it solve exactly?
Another thing happens is when I use npm install, I see a lot of warnings in the console that
WARNING: X package is deprecated
But when I run npm outdated I see that all packages are all fairly up to date (all match the recommended version to download), so I assume this might be a dependency for a certain package. But does it affect our work negatively? Why does this happen?
For the packages I download, I generally look for packages that have in the 6 digits Weekly Downloads from npm so I don't think we are using unfamiliar packages.
I am asking these questions because they have been asked to me but I don't have a straight answer to them.
Thank You!
I don't understand how npm install -f works
can someone help me to identify what the issues is to my cli code when uninstalling the npm packages. When i run this cli code (in the picture below), the npm not unistalling the packages but instead added it to my node_modules. I hope someone in this community can solve my problem and bring any solutions that i can try to solve this weird problem to me.
NPM package is being removed. The one which are being shown as added are already remaining packages. This is the way node shows output in terminal.
To verify, check your pacakge.json, there won't be any package named webpack-config.
I'm trying to understand if it is necessary to run a npm install after upgrading node/npm from 6.x to 8.x. If so, can you please explain why this is done? I had a hard time finding some documentation around this.
You should at least run npm rebuild.
Some packages may choose to do things differently in a different Node.js environment, particularly when it comes to binary modules.
Breaking my head to get over that error. I've tried every forum but still I can't find a proper solution. I also uninstalled and reinstall npm and still same issue.
Please save me!
npm error
and also
log
ta!
Just a wild guess:
remove .npm-modules in your home folder
remove modules from the project you are using
npm install, all should be fine
Use homebrew to install npm and nodejs. Write the command as shown below:
brew install node . Once it is successfully installed check it with node -v.
For more details you can go through this tutorial
I am trying to install Satellizer.
But getting error.
Can you guide me to understand whats this error is, and how can I fix this.
I have node version v5.1.0 and npm version 3.5.2
Looks like you have the Satellizer as a decency inside your package.json
Or
That the project name is the same of one your depended package(s)
If it not a depended package, there used to be some error with npm v3.5.X so try to update your npm version and then re-install it.
I would also recommend to test it with node v4.X since v5 might contain those kind of bugs