Migrate/deprecate packages using former "ipld" package

[vmx]

ipld-resolver has been renamed to ipld, hence all packages which depend on the old ipld won't receive any updates and it will be confusing as it looks like there's a new version of ipld available, but in reality it's a completely different thing.

Packages using the old "ipld" should either be deprecated or adapted so they don't use "ipld" anymore. According to npm those packages are:

Those are all related to IPRS. Is that still a thing? What should we do with the repositories below?

• https://www.npmjs.com/package/ipfs-record
• https://www.npmjs.com/package/abstract-record-store
• https://www.npmjs.com/package/ipfs-kad-record-store
• https://www.npmjs.com/package/interface-record-store
• https://www.npmjs.com/package/libp2p-kad-record-store
• https://www.npmjs.com/package/ipfs-drs

What about:

• https://www.npmjs.com/package/ipfs-ipld
  It now links to the js-ipld repo, but surely isn't the same thing. I think that one should also be deprecated.

Already deprecated:

• https://www.npmjs.com/package/merkle-trie

[vmx]

It's unfortunate that ipld used to be another library. Hence most of the packages listed on https://www.npmjs.com/package/ipld?activeTab=dependents don't really depend on ipld as they depend on the old version.

I use the dependents information to see which things need to be updated when we do breaking changes, but sadly this doesn't work here anymore. The only ones actually depending on the current ipld package is ipfs and ipfs-unixfs-engine as far as I can tell.

[daviddias]

All of the record modules are 2+ years old. They are part of the first gen of libp2p modules, one that never saw the light of the day given it was too different from go-ipfs. Do not worry about those.

ipfs-ipld is confusing. @dignifiedquire can you unpublish it please?

[vmx]

It would be so cool if we could unpublish these old modules, but sadly that's not possible anymore.

Edit: I just read the unpublish guidelines from npm. It looks like it would be possible. @diasdavid I'd be happy to drive that if you think it would make sense and make me a publisher of those packages, so that npm knows that i'm legit to do so.

[dignifiedquire]

but isn’t there something like a deprecation thing that one can use?

…

On 23. Apr 2018, 15:15 +0200, Volker Mische ***@***.***>, wrote: It would be so cool if we could unpublish these old modules, but sadly that's not possible anymore. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.