Skip to content

Conversation

@bcomnes
Copy link
Contributor

@bcomnes bcomnes commented Sep 23, 2015

I believe this should normalize behavior between npm2 and 3 once the upstream path export is fixed: ipfs/npm-kubo#2

Closes #20

I believe this should normalize behavior between npm2 and 3 once the upstream path export is fixed: ipfs/npm-kubo#2
@bcomnes
Copy link
Contributor Author

bcomnes commented Sep 23, 2015

Ok I think this is good to go now. What happens when we re-run the tests?

@daviddias
Copy link
Member

Nice! tested this and also tested this new ipfsd-ctl on node-ipfs-api and every test passes, should solve the issue for everyone, including ipfs-inactive/js-ipfs-http-client#64

thank you @bcomnes :)

daviddias added a commit that referenced this pull request Sep 25, 2015
Require "go-ipfs" directly to get exe path.
@daviddias daviddias merged commit 887d111 into ipfs:master Sep 25, 2015
@RichardLitt RichardLitt mentioned this pull request Sep 25, 2015
65 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

go-ipfs is required from the top-level module

2 participants