ipfs-shipyard/npm-on-ipfs

Can npm publish work for registry.js.ipfs.io?

Closed this issue · 6 comments

alanshaw commented

I have registry.js.ipfs.io setup as my registry in ~/npmrc. Whenever I npm publish I have to remember to add --registry=https://registry.npmjs.com or it fails. For js-ipfs I get the following error but I think I get a different error for other modules.

npm notice 
npm http request PUT https://registry.js.ipfs.io/ipfs
npm http 413 https://registry.js.ipfs.io/ipfs
npm ERR! registry error parsing json
npm ERR! publish Failed PUT 413
npm ERR! Unexpected token < in JSON at position 0
npm ERR! <html>
npm ERR! <head><title>413 Request Entity Too Large</title></head>
npm ERR! <body bgcolor="white">
npm ERR! <center><h1>413 Request Entity Too Large</h1></center>
npm ERR! <hr><center>nginx/1.14.0</center>
npm ERR! </body>
npm ERR! </html>

Is it possible to proxy it or configure npm with a different registry for publishing or something?

daviddias commented

Yes please! Or have #50 so that npm publishes use npm and installs use ipfs-npm

achingbrain commented

I think you can also set registry in the package.json of a project to ensure it's always published to that registry.

  • 👍2
alanshaw commented

This is rad, and I can confirm it works with interface-ipfs-core but I think the 1MB limit might be a little low - js-ipfs package size is 16MB I think.

https://unpkg.com/ipfs@0.32.2/dist/

achingbrain commented

The limit should be 1GB. Where are you seeing it set to 1MB?

alanshaw commented

*rubs eyes* oh yea!

achingbrain commented

*phew*