What is the difference between js-ipfs-api and js-ipfs?

From @RichardLitt on Fri Oct 09 2015 18:11:45 GMT+0000 (UTC)

There are two repositories in the ipfs organization: node-ipfs-api and ipfs-api. What’s the difference between the two? Are they interchangeable? If one is a node implementation and the other a node digester, will node-ipfs-api eventually use node-ipfs?


Copied from original issue: https://github.com/ipfs/faq/issues/60

From @whyrusleeping on Fri Oct 09 2015 18:13:25 GMT+0000 (UTC)

the node-ipfs-api is api bindings for the ipfs api written in node.

node-ipfs is the actual node.js implementation of the ipfs protocol

From @VictorBjelkholm on Fri Oct 23 2015 15:46:42 GMT+0000 (UTC)

I’m thinking if the repos should change name to JS to reflect the scope. Focus seems to be on node+browser and then it’s really javascript, not just node.

From @jbenet on Fri Oct 23 2015 17:42:20 GMT+0000 (UTC)

good points. it would also help to ease confusion to call all the things
“js-” instead of “node-” as “node” has many meanings in IPFS land.

On Fri, Oct 23, 2015 at 8:46 AM, ᴠɪᴄᴛᴏʀ ʙᴊᴇʟᴋʜᴏʟᴍ notifications@github.com
wrote:

I’m thinking if the repos should change name to JS to reflect the scope.
Focus seems to be on node+browser and then it’s really javascript, not just
node.


Reply to this email directly or view it on GitHub
https://github.com/ipfs/faq/issues/60#issuecomment-150612981.

From @RichardLitt on Mon May 02 2016 19:25:31 GMT+0000 (UTC)

These are all called js- now. :dancing_women: