6

Closed

Broken package manager in Beta

description

The package manager in Beta version is worse than the one in Alpha.
  • It does not display the list of packages.
  • The Install button is inactive even if the typed package name is valid
  • Enter button works and installs the package however package.json file is not updated
What happened with this ? It was working quite OK..

file attachments

Closed Sep 16 at 6:13 PM by RickWinter

comments

BartRead wrote Apr 6 at 12:09 AM

Thanks for reporting this.

Can you let me know which versions of node, npm, and Visual Studio you're using, please?

To find out the node version you're running, from a command window execute:

node --version

Likewise for the npm version please execute:

npm --version

(You'll need node and npm to be on your PATH; if not just execute these commands in your node install directory.)

Thanks!

mikeluan wrote Apr 7 at 3:35 AM

Having same blank-NPM issue here,
npm version: 1.3.14
node version: 0.10.22

The issue around package.json however, occured during alpha for me already.. not fixed till now..

Will provide info if needed, NTVS is really something worth diggin!

kubal5003 wrote Apr 7 at 9:36 AM

Hey,

my node version: v0.10.21
my npm version: 1.3.11

kubal5003 wrote Apr 7 at 9:39 AM

Sorry, forgot about Visual Studio:
Visual Studio 2013 Version 12.0.30110.00 Update 1

Node & npm are in my path. I was able to use package manager in the alpha version of ntvs both in VS2012 and VS2013.

BartRead wrote Apr 8 at 4:30 PM

Hey, thanks for this. What are the exact symptoms? Does it just hang for ages on the screen where it's loading/refreshing the package list (there should be a non-deterministic progress bar in view)?

(I ask only because I've noticed the refreshing the package list is now starting to take really quite a lot time, partly because the number of packages in the npm repo is increasing rapidly, but I think mainly because the repo is sluggish. Also the amount of padding in the data has massively increased, though I can't say whether or not this is a factor in the slow retrieval in the package list - that may not be added until the client side in npm itself rather than by the web service.)

BartRead wrote Apr 8 at 4:32 PM

FYI, I'm on node 0.10.26 and npm 1.4.4.

If you're able could you try upgrading to more recent versions of node and npm, please? I'd suggest you rename your current node folder so that you can revert back to it afterwards, in case your projects depend on the old versions.

Thanks!

BartRead wrote Apr 8 at 4:56 PM

Oh, one more thing. I don't suppose there's any chance you're being hit by this, is there?

http://blog.npmjs.org/post/78085451721/npms-self-signed-certificate-is-no-more

This caused total carnage in the node dev community at the end of Feb/beginning of March.

To find out, just execute an npm install command from the command line. E.g.,

npm install express

would do the trick nicely. Also, try a command line search: "npm search express", for example.

JoelThemmen wrote Apr 8 at 8:14 PM

I am experiencing a similar experience ...

Node: 10.26 and 11.9 (I switched back and forth to test)
NPM: 1.4.3

The NPM dialog comes up and notifies that it is "Loading the published package list"

Then it opens with no items (for any of the 4 values in the drop down - I ran through all 4)

When I search for "Express" (for example) by entering "Express" and hitting "Enter" the list is not populated but Express was downloaded and installed (I can watch it do it's work at the bottom of the dialog)

To recap ...

1.) "Search"" installs what is typed into the top text box rather than adding it to the dialog
2.) The central portion (list) of the dialog is never populated
3.) The "Install" button is never "ungrayed" - likely because there is no content in the list portion of the dialog
4.) The bottom text box is fixed at "READY" with the "Cancel" button always grayed out.
5.) A command line search does bring back the appropriate list (albeit quite slowly)

It looks like it simply takes the first match from whatever is type in and installs that (but that is a wild guess) ...

Hope this helps ...

Joel

kubal5003 wrote Apr 10 at 12:46 PM

Hey,
for me it's almost identical to what Joel described. The list simply never gets populated.
I watched a video of how it was supposed to work and it seems to me that the problem lies only in getting the list to populate.

After I installed NTVS I was on mobile connection and the package list seemed to load forever - and it did not finish in half an hour. (mobile connection = HSPA 7.2)

Later when I was using normal connection (60mbit/s) the loading seemed to be quick but nothing ever appeared on the list.

Hope this helps

Zooba wrote Apr 23 at 6:11 PM

As Bart mentioned, npm recently updated their server with a new certificate which will prevent older versions of npm from working.

To resolve, you need to install a newer version of npm. Sorry we couldn't provide a more useful message in NTVS, but their change caught us by surprise as well.

johara56 wrote Apr 23 at 9:47 PM

I have the same issue as described by Joel. The package is installed but the package.json is not updated correctly and must be hand edited to make it persist

kubal5003 wrote Apr 23 at 11:00 PM

After having a little trouble with updating npm I managed to do it and now with
Node v 0.10.26
Npm v 1.4.7

I still have the same problem. It seems to me that it is not in any way related to npm since I was able to do everything from the command line all the time. Package list still not populated :(

mpatrone wrote May 20 at 9:38 PM

I have the same interface problem. Package manager allows sercahing and installing packages but does not show the ones installed locally and globally.
Relevant versions are:
VS2013 Ultimate Update2 RC
node v0.10.28
npm 1.4.9
NTVS 1.0 beta Fri Apr 4, 2014 at 8:00 AM
Tried to reinstall npm to downloading zip file and unzipping it to the nodejs directory (c:\Program Files\nodejs).
To no avail.