feat: support window.ipfs.enable()

[lidel]

This PR enables support for asynchronous window.ipfs.enable :

const { ipfs, provider } = await getIpfs({
  tryWindow: true,
  permissions: { commands: ['add','cat','id', 'version'] },
  tryJsIpfs: true,
...

Closes #1
cc ipfs/ipfs-companion#589

• support for asynchronous window.ipfs.enable
• support passing commands and experiments to window.ipfs.enable
  • Other providers may want to add support for those in the future, so those could be top-level config options.

[lidel]

@fsdiogo are you still maintaining this repo, or want to hand it over?
Would need NPM publishing rights as well.

[hacdias]

Loooks good!

[fsdiogo]

@fsdiogo are you still maintaining this repo, or want to hand it over?
Would need NPM publishing rights as well.

I wouldn't mind maintaining this repo, but I've been removed from the ipfs-shipyard org, so I don't have any perms on this repo now.

I've added you and Oli to the npm admin list, so you should be good to go:

Ping me if otherwise!

[lidel]

@fsdiogo added you back as a Collaborator to this repo :)

[lidel]

@fsdiogo I see this repo was not set up with aegir: how did you build & release it to NPM before?

I want to release this as 0.2.2 to remove deprecation warning about window.ipfs v1,
but afraid to make invasive changes by introducing aegir in patch release.

[fsdiogo]

@lidel I just published v0.2.2.

There is no need to build, it works out of the box. Yeah, I opted out of using aegir as I didn't see any benefits of using it for this, but feel free to add it if you think otherwise!

Publish to to npm:

• Update the package.json to the desired version
• Commit to GitHub (e.g. 883b4c7)
• Create a tag with the version and push it
• Run npm publish on the project folder in the terminal