Comparing version 0.4.1-hacky2 to 0.4.2-npmfix2
@@ -7,3 +7,3 @@ 'use strict' | ||
var version = require('./package.json').version | ||
version = version.replace(/-hacky[0-9]+/, "") // remove superfluous -suffix. | ||
version = version.replace(/-npmfix[0-9]+/, "") // remove superfluous -suffix. | ||
@@ -10,0 +10,0 @@ var depPath = require.resolve('go-ipfs-dep') |
{ | ||
"name": "go-ipfs", | ||
"version": "0.4.1-hacky2", | ||
"version": "0.4.2-npmfix2", | ||
"description": "Install the latest go-ipfs binary", | ||
@@ -18,3 +18,3 @@ "main": "index.js", | ||
"dependencies": { | ||
"go-ipfs-dep": "0.4.1", | ||
"go-ipfs-dep": "0.4.2-1", | ||
"go-platform": "^1.0.0", | ||
@@ -21,0 +21,0 @@ "gunzip-maybe": "^1.3.1", |
@@ -35,7 +35,7 @@ # npm-go-ipfs | ||
> ipfs version | ||
ipfs version 0.4.1 | ||
ipfs version 0.4.2 | ||
> npm install go-ipfs | ||
> node_modules/.bin/ipfs | ||
ipfs version 0.4.1 | ||
ipfs version 0.4.2 | ||
``` | ||
@@ -80,3 +80,3 @@ | ||
1. **Clean up bad stuff:** unpublish all modules with this exact same `<go-ipfs-version>` | ||
2. **Add a "hacky" version suffix:** use version: `<go-ipfs-version>-hacky<num>` | ||
2. **Add a "npmfix" version suffix:** use version: `<go-ipfs-version>-npmfix<num>` | ||
3. **Publish version:** publish the module. Since it's the only one with the go-ipfs version, then it should be installed. | ||
@@ -86,11 +86,11 @@ | ||
Well, if you previously published npm module `go-ipfs@0.4.0` and there was a problem, we now must publish a different version, but we want to keep the version number the same. so the strategy is to publish as `go-ipfs@0.4.0-hacky1`, and unpublish `go-ipfs@0.4.0`. | ||
Well, if you previously published npm module `go-ipfs@0.4.0` and there was a problem, we now must publish a different version, but we want to keep the version number the same. so the strategy is to publish as `go-ipfs@0.4.0-npmfix1`, and unpublish `go-ipfs@0.4.0`. | ||
> Why `-hacky<num>`? | ||
> Why `-npmfix<num>`? | ||
Because it is unlikely to be a legitimate go-ipfs version, and we want to support go-ipfs versions like `floodsub-1` etc. | ||
> Do i have to say `-hacky<num>` or can i just use `-<num>`? | ||
> Do i have to say `-npmfix<num>` or can i just use `-<num>`? | ||
`-<num>` won't work, as [link-ipfs.js](./link-ipfs.js) expects `-hacky<num>`. If you want to | ||
`-<num>` won't work, as [link-ipfs.js](./link-ipfs.js) expects `-npmfix<num>`. If you want to | ||
change the convention, go for it, and update this readme accordingly. | ||
@@ -97,0 +97,0 @@ |
10918
+ Addedgo-ipfs-dep@0.4.2-1(transitive)
- Removedgo-ipfs-dep@0.4.1(transitive)
Updatedgo-ipfs-dep@0.4.2-1