Deprecate in favour of ipfs-provider

[lidel]

Context

window.ipfs-fallback was created as an exploration in opportunistic upgrade of IPFS experience using API exposed by ipfs-companion.

Since then, we created more advanced ipfs-redux-bundle for use in ipfs-webui and @fsdiogo started work on extracting logic into a new, framework-and-backend-agnostic library ipfs-provider, which supports window.ipfs as one of its backends.

This means we now have three libraries, and should start planning convergence around the versatile ipfs-provider.

Deprecation Plan

• ensure ipfs-provider provides same features as window.ipfs-fallback
  (does not need to be same syntax, but should have more or less feature-parity)
  • window.ipfs.enable is supported (Add support for window.ipfs.enable({commands, experiments}) ipfs-shipyard/ipfs-provider#1)
• Test and update window.ipfs docs to point at ipfs-provider
  • fix: suggest ipfs-provider for window.ipfs fallback ipfs/ipfs-docs#207
• Update in-web-browsers/README.md
• deprecate window.ipfs-fallback
  • update README: indicate it is DEPRECATED and replaced with ipfs-provider
    (example of deprecated project)
  • mark deprecated at NPM
• Optional: PR external projects that use window.ipfs-fallback Marked deprecated at NPM instead, with message pointing at ipfs-provider

Refs

cc ipfs/in-web-browsers#137 ipfs/ipfs-companion#589

[lidel]

@alanshaw do you mind releasing a patch release so description on NPM gets updated with deprecation notice and then mark it as deprecated on NPM?

I feel that should point people at the most flexible library and remove a lot of a lot of confusion.

[alanshaw]

You're already a maintainer on npm for this package - any chance you can do the publish?

[alanshaw]

Oh, you should also use https://docs.npmjs.com/cli/deprecate

[lidel]

Ah.. I've seen only your avatar and made wrong assumption ;-)

Published + added deprecation message.
Will now archive this repo.