-
Notifications
You must be signed in to change notification settings - Fork 19
Deprecate in favor of npm-go-ipfs #45
Comments
I don't see any good reason to keep both, but I also have the least context. |
The changes I made to the This module should be deprecated with a message saying to use See also: #42 |
I've added a deprecation warning to If everyone's happy we can merge that and move this repo to |
Now that the |
Quite a few projects have go-ipfs-dep as a dependency, would be good to send them a PR to switch if we're not going to be publishing updates anymore: https://ipfs.ecosystem-dashboard.com/packages/1859?direct=true |
@andrew has a good point. At a very minimum, we need:
Then,
I can help with this if |
Deprecated on NPM, will move to https://github.com/ipfs-inactive/ shortly |
So.. we have two ways of getting go-ipfs via NPM:
Alex fixed a bunch of stuff in ipfs/npm-kubo#26, and stated that [npm-go-ipfs-dep] should be retired.
Should we deprecate
go-ipfs-dep
and point people atgo-ipfs
?Any reason for maintaining both?
cc @olizilla @achingbrain @hugomrdias @aschmahmann @vasco-santos @Gozala @andrew
The text was updated successfully, but these errors were encountered: