version available via npm (0.2.1 or 0.2.3)

[tomyan]

Hi Kris

Seems that the tagged release for 0.2.5 has 0.2.3 in the package.json. Funny thing is, when I look on the npm site, it says that the latest is 0.2.1 (is that an npm bug?):

http://search.npmjs.org/#/promised-io

When I install it on the command line:

mac:~/node-projects/litmus.js> npm install promised-io
[email protected] ./node_modules/promised-io

I was able to confirm that npm had installed the version it said it had (or so I thought):

mac:~/node-projects/litmus.js> grep version node_modules/promised-io/package.json 
  "version": "0.2.3",

I managed to track it down to have the same contents of the commit that was tagged as 0.2.5. Confused me for quite a while. Anyway, let me know if there's an npm bug there to be reported.

Thanks

Tom

[kriszyp]

Thats because promised-io is published through dojo foundation rather than
npm and linked to the npm repo, which doesn't require the version numbers in
package.json. Ill try to get them updated on the next release.
On Oct 15, 2011 7:54 AM, "Tom Yandell" <
[email protected]>
wrote:

Hi Kris

Seems that the tagged release for 0.2.5 has 0.2.3 in the package.json.
Funny thing is, when I look on the npm site, it says that the latest is
0.2.1 (is that an npm bug?):

http://search.npmjs.org/#/promised-io

When I install it on the command line:

mac:~/node-projects/litmus.js> npm install promised-io
[email protected] ./node_modules/promised-io

I was able to confirm that npm had installed the version it said it had (or
so I thought):

mac:~/node-projects/litmus.js> grep version
node_modules/promised-io/package.json
"version": "0.2.3",

I managed to track it down to have the same contents of the commit that was
tagged as 0.2.5. Confused me for quite a while. Anyway, let me know if
there's an npm bug there to be reported.

Thanks

Tom

Reply to this email directly or view it on GitHub:
#22