how-to-npm chapter 08 publish - Cannot get publish to run

[hferguson]

Hello,
I've seen this documented but none of the solutions work. When I run npm publish, I get the following:
E:\development\nodejs\how-to-npm>npm publish
npm ERR! publish Failed PUT 404
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "E:\development\nodejs\node.exe" "C:\Users\Hugh\AppData\Roa
ming\npm\node_modules\npm\bin\npm-cli.js" "publish"
npm ERR! node v4.2.2
npm ERR! npm v3.5.0
npm ERR! code E404

npm ERR! 404 missing : @hferguson/how-to-npm
npm ERR! 404
npm ERR! 404 '@hferguson/how-to-npm' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)

npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! Please include the following file with any support request:
npm ERR! E:\development\nodejs\how-to-npm\npm-debug.log

Oddly though if I run how-to-npm right after, it tells me that my solution is correct. However, eventually I get an unhandled exception by chapter 10 if I leave chapter 08 in this state.
Here is the log file.

npm-debug.txt

Any suggestions?
-Hugh Ferguson
PS I also tried uninstalling and reinstalling the how-to-npm package, which only succeeded after a reboot.
PPS This is Windows 7 environment.

[aliivibrio]

Hugh,

I encountered the same thing. After a bit of digging, I found that the mock registry was failing to write the .tgz file, due (I think) to writeFileSync on Windows not being able to create a file if the directory you're creating it in doesn't yet exist. I hope to throw a fix together, but you should be able to work around it by:

1. Going to
   C:\Users\Hugh\.config\how-to-npm\registry\@hferguson\how-to-npm\-
2. Creating an empty @hferguson folder.

Thanks for posting this, it made me aware that I hadn't messed something up big time!

[betaalpha987]

Well done benetd, that fixed my identical issue too! It still occurs over a year later. I confess, I wasn't following the instructions in Free Code Camp about using cloud9, I was using my local PC instead (which runs Win 10, hence the problem occurring in Windows). Due to having bad experiences with Cloud9 when trying the FCC MongoDB challenge, and had to give up on it.

[nl-x]

@Benetd Thank! This solved my issue as well. The only slightly interesting thing in my case is that my name contains a '-' (dash). Maybe it is related.

And the really frustrating part is, in my case, this would crash the local webserver running the mock npmjs service. It turns out you can restart the service though by running exercise 2 again...

[erichartline]

Yes, thank you @Benetd! Just ran into the same issue using Windows 10, but that fixed it immediately. Much appreciated.

[shokry-suleiman]

@Benetd
thanks