how-to-npm icon indicating copy to clipboard operation
how-to-npm copied to clipboard

Step 8 - "Publish" doesn't work on Windows 10. Localhost:15443 not responding

Open brentpayton opened this issue 8 years ago • 6 comments

Step 8 consistently fails on Windows 10 but passes on MacOS. It appears that the local server on port 15443 has exited or otherwise isn't responding when this failure occurs.

npm-debug.log.txt

brentpayton avatar Feb 05 '17 16:02 brentpayton

NPM version 4.1.2 Node version 6.9.4

brentpayton avatar Feb 05 '17 16:02 brentpayton

Hello 👋

Thanks for reporting this. The port number is declared as hard cording, so I put a bug label on this issue.

$ grep -irl 15443 .
./assets/registry/wrappy/body.json
./lib/registry.js
./workshop-npmrc

As a solution, we have two options:

  • Find an available port, and use it in the files that should be created dynamically
  • Display an error in exercises if it's used

I will consider a better way, but I will be glad to support anyone including you if someone has an interest in working on this.

watilde avatar Feb 05 '17 17:02 watilde

Nice package to create a patch with https://github.com/sindresorhus/get-port

watilde avatar Feb 16 '17 16:02 watilde

But I got:

npm ERR! publish Failed PUT 404
npm ERR! code E404
npm ERR! 404 missing : @shadowrz/sample-npm-package
npm ERR! 404
npm ERR! 404  '@shadowrz/sample-npm-package' 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! A complete log of this run can be found in:
npm ERR!     C:\Users\Administrator\AppData\Roaming\npm-cache\_logs\2017-04-14T10_53_14_504Z-debug.log

@brentpayton @watilde EDIT: When I access registry over HTTP:

{"error":"missing"}

ShadowRZ avatar Apr 14 '17 10:04 ShadowRZ

@ShadowRZ It seems a different issue. Could you please open another issue and share your npm-debug.log?

watilde avatar Apr 14 '17 11:04 watilde

This issue was confirmed as a bug already as it's labelled. how-to-npm doesn't work if the user is using the same port number(15443).

watilde avatar Apr 14 '17 11:04 watilde