fix(cli): add output for cli init

[victorb]

Shows exactly same information as go-ipfs except for change of the cmd +
cat so ipfs cat turns into jsipfs files cat instead. Ref: issue #286

[victorb]

This is the output of init with this change:

$ export IPFS_PATH=~/.ipfs-js
$ node src/cli/bin.js init 
initializing ipfs node at /home/victor/.ipfs-js
generating 2048-bit RSA keypair...done
peer identity: QmP7HvVg8wJV1YvbnmFsnxAP5ULyZaeCxhJx12kizyybfL
to get started, enter:

     jsipfs files cat /ipfs/QmegvLXxpVKiZ4b57Xs1syfBVRd8CbucVHAp7KpLQdGieC/readme

[victorb]

Not sure why Travis is failing here, working fine in CircleCI

[daviddias]

@victorbjelkholm while you are this, can you alias ipfs files {cat, add, get, ls} to ipfs {cat, add, get, ls}, so that we can use the Sharness and Benchmark tests?

[daviddias]

Isn't this just a console.log? All invisible logs should be through debug (http://npmjs.org/debug)

[victorb]

Almost, it's console log with the ability of deciding if next message should go on a new line or not. Necessary for the generating keys message, which prints "done" after it's done.

[victorb]

@diasdavid Sure, I'll create the aliases in a different PR though.

[dignifiedquire]

This will fail on node 4 and 5, (default arguments are only supported in node 6)

[victorb]

Oh, I was sure that js-ipfs was compiled, even when used from node. Is that not correct?

[dignifiedquire]

We do provide a compiled version when publishing do npm, but the tests run on node against the original source atm.

[victorb]

Shouldn't the tests run against the compiled version that we distribute rather than the source we develop with? Anyways, I'll fix this but worth thinking about.

[dignifiedquire]

If you npm install it, you can use both versions.

[victorb]

Ah, but require('ipfs') would use the compiled version right?

[dignifiedquire]

Yes. And the tests in the browser do run against the compiled version