Sometimes, when I right click npm and select "Manage npm Modules", the package manages says "Loading published package list", but it comes back empty. See screenshot here: 
I am still able to install packages using the npm command, but they are not added to packages.json and I have to call npm init manually.
Comments: from mousetraps: and now in a more readable form :) @martin_codeplex Thanks, though I believe there are actually multiple issues. The parser issue is recent (the packagecache file now has a few arrays of homepages whereas before it was just a string). Luckily it repros on my box (unluckily it will repro on everyone's box...), and I should have a fix in soon. There's also Ergwun's issue - the package list is being parsed properly, just not displayed, which leads me to believe it's a UI threading issue. I'm investigating, but don't have a lead on that yet (what surprises me is that it's consistent) And there's an out of memory issue as well, which we hope to address by moving to a db instead of reading the json file every time. @maheshw - based on your screenshot, you don't seem to have the right version (with the logging). Unfortunately mostly everyone will be failing with the same error now, though, so I'll let you know when there's a new build available.[0A][0A]for now, DON'T REFRESH THE CATALOG. It will break with the parsing error @martin_codeplex mentioned :(
I am still able to install packages using the npm command, but they are not added to packages.json and I have to call npm init manually.
Comments: from mousetraps: and now in a more readable form :) @martin_codeplex Thanks, though I believe there are actually multiple issues. The parser issue is recent (the packagecache file now has a few arrays of homepages whereas before it was just a string). Luckily it repros on my box (unluckily it will repro on everyone's box...), and I should have a fix in soon. There's also Ergwun's issue - the package list is being parsed properly, just not displayed, which leads me to believe it's a UI threading issue. I'm investigating, but don't have a lead on that yet (what surprises me is that it's consistent) And there's an out of memory issue as well, which we hope to address by moving to a db instead of reading the json file every time. @maheshw - based on your screenshot, you don't seem to have the right version (with the logging). Unfortunately mostly everyone will be failing with the same error now, though, so I'll let you know when there's a new build available.[0A][0A]for now, DON'T REFRESH THE CATALOG. It will break with the parsing error @martin_codeplex mentioned :(