This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
We are renaming the prefix of our JavaScript modules from 'node-' to 'js-' #32
Comments
This was referenced Oct 28, 2015
Merged
Closed
Closed
Closed
just saw this, really good decision! |
thank you, @dignifiedquire :) |
What, you dont want to change ipfs node to hub everywhere? This is a good decision 👍 |
Don't forget:
Should've used IPNS for everything I guess :P |
This was referenced Oct 29, 2015
Closed
Closed
Merged
Closed
done :) |
RichardLitt
added a commit
to RichardLitt/ipfs
that referenced
this issue
Oct 31, 2015
This follows ipfs/js-ipfs#32.
RichardLitt
added a commit
to RichardLitt/ipfs
that referenced
this issue
Nov 16, 2015
This follows ipfs/js-ipfs#32.
MicrowaveDev
pushed a commit
to galtproject/js-ipfs
that referenced
this issue
May 22, 2020
…same-hashes fix: make sure hashes are the same after shard changes
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As discussed on the Oct 26 Sprint meeting, we will be renaming the prefix of any of our github repos that contain any JavaScript module, from 'node-' to 'js-'.
This decision came from hearing the feedback from the IPFS community, where there was always some confusion with the words 'node' and 'ipfs' and also a the lack of clarity if a module is supposed to be Node.js only. 'node' is a very overloaded word in the IPFS context.
This doesn't mean however that we will be leaving the npm ecosystem, npm will still be the tool of choice when it comes to publishing and installing this JavaScript modules.
We will be rotating the repo names starting of today, this should not change the behaviour when installing one of these modules or break any CI tools, since we always published to npm without the prefix.
List of repos suffering this change (let us know if we miss any):
The text was updated successfully, but these errors were encountered: