published npm package is not visible npm - node.js

I'm new to npm, recently I published an npm package 'mango-aliyan' and I can see it at https://www.npmjs.com/~shakkirptb, but https://www.npmjs.com/package/mango-aliyan is showing 404!
what am I missing here?
Thanks for your help

I've had a similar issue recently and I believe NPM does not immediately publish packages. There could be a number of reasons and I'm sure it's done on purpose.
If you wait about 5-10 minutes your package will be publically visible. I have visited the link to your package and it seems to be working just fine.

Related

How to install a deprecated version of uws

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.

Different NPM version used when generating React app

When I try to create the starter React tutorial app using powershell, I get the below error:
"You are using npm 2.15.12 so the project will be boostrapped with an old unsupported version of tools".
"Please update to npm 3 or higher for a better, fully supported experience".
However, my NPM version is 6.11.3 as seen below.
What I have tried:
I have ran powershell as admin as answered in this question and restart.
I have also uninstalled and reinstalled Nodejs completely.
So after an extra hour digging around, I saw a few posts with similar (but not exactly) the same issue. I decided to install Yarn and install with that.
After install, I ran yarn cache clean and ran npx create-react-app your-app and it worked. Sorry for bothering you all.
I had the same problem. I'm running WSL with ubuntu, and yarn cache clear didn't work, but I noticed a node modules directory created in the project. I think it was messing with the node version so I deleted it. It worked

I published one package on npm, but it's not showing in the search list when i am going to search

I published one package as a public & i am trying to search it on npm
(https://www.npmjs.com/), but there is no package available with that name on npm.
Tried with:
npm install package-name -> working fine
Here is the package link:
https://www.npmjs.com/package/and-or-search
Is there any thing i am missing?
The npm website takes time to show the latest packages or package versions because of the delays in CDN, website cache etc.
But it will show up eventually. Meanwhile, you can check for the package with:
npm show <package-name>
This will output all the versions of the package as well so you can be confident that the package exists or the latest version is published.
Your package now shows up correctly in npm website at https://www.npmjs.com/package/and-or-search
It takes some time for website to show the latest version, but it also takes some time for npm show <package-name> From my experience I haven't noticed difference between the command and between the website. You should also receive email.
I recommend waiting a few minutes.

NPM uninstall packages not working

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.

Create an offline installer of npm package

Problem:
I have a very flaky internet connection at my place.
Due to this when I try to do
npm install -g glup
it stops the download before completion.
I have tried downloading several times but all in vain.
Thinking about my options
I have a friend in other city with high speed internet, I can ask him to somehow package the glup and provided it to me using dropbox, then i can use any download manager to download it partially with my flaky connection.
But the sad thing is he doesn't know how to do it. (help on this front is also appreciated)
Can anyone help me out with this situation?
P.S: I am doing a course from Udacity and due to my flaky internet connection I am kind of facing lot of issues.
According to the docs, npm install supports installing from a tarball file sitting on your filesystem. So, as long as your friend can create and supply you a tarball of the npm package you are looking for - you should be good to go.
Below is a quote from the docs.
UPDATE: To create a tarball file from an npm package, you can just run npm pack package_name. For example,
npm pack underscore
will create a .tgz file for the latest version of underscore.js npm package. See the documentation for npm pack here.
Not answering directly your question, but I was just struggling with network connection behind a corporate firewall with npm for hours. Then I tried yarn, the package manager from Facebook. Wow, it worked like a charm, install of the package I needed plus deps. done within a minute.

Resources