It's not done. But, enough of it may be done to get something off the ground. Currently, it would appear the final remaining components needed for js-ipfs to be properly usable in the browser are the relay code and the dht. As of writing, js-ipfs is at 0.23, and one of those two required features WILL ship in 0.24, while the other MAY be delayed to 0.25.
go-ipfs currently has all the components in place already, but it can't be used in the browser without prior installation.
It should be noted that both go-ipfs and js-ipfs have pretty much equivalent APIs, and I have verified that js-ipfs and js-ipfs-api hooks are basically identical (with some disparity based on unimplemented hooks on each side). So, code written for node can be used with either backend without incident. I have not yet checked whether the situation is the same from the Go POV.
It's not done. But, enough of it may be done to get something off the ground. Currently, it would appear the final remaining components needed for js-ipfs to be properly usable in the browser are the relay code and the dht. As of writing, js-ipfs is at 0.23, and one of those two required features WILL ship in 0.24, while the other MAY be delayed to 0.25.
go-ipfs currently has all the components in place already, but it can't be used in the browser without prior installation.
It should be noted that both go-ipfs and js-ipfs have pretty much equivalent APIs, and I have verified that js-ipfs and js-ipfs-api hooks are basically identical (with some disparity based on unimplemented hooks on each side). So, code written for node can be used with either backend without incident. I have not yet checked whether the situation is the same from the Go POV.