dist-tags parsed wrong?

[aikomastboom]

Hi,

http://registry.npmjs.org/minijasminenode/

has:

"dist-tags": {
  "latest": "0.2.7",
  "canary": "0.3.0"
}

when asking sinopia to proxy:

uplinks:
  npmjs:
    url: https://registry.npmjs.org/

sinopia returns:

"dist-tags": {
"latest": "0.3.0",
"canary": "0.3.0"
}

In my case braking: https://github.com/angular/protractor/blob/master/package.json

  "minijasminenode": ">=0.2.7"

[aikomastboom]

cross-reference: angular/protractor#611

[rlidwka]

latest tag is intentionally ignored to avoid npm bugs (see #50)

although I'm thinking about changing it back recently

[yannickcr]

We also have some problems related to this issue but with unpublished versions.

For example we are currently using the simple-xmpp package that have 0.1.18 as the latest version but also have an unpublished one in 0.1.91.

npm:

"dist-tags": {
  "latest": "0.1.18"
}

Sinopia:

"dist-tags": {
  "latest": "0.1.91"
}

Typing npm install simple-xmpp with Sinopia will install the 0.1.91, so the unpublished and wrong one.

Since the original npm bug is now fixed, is would be nice to stop ignoring the the latest tag to avoid those kind of problems.

[rlidwka]

Since the original npm bug is now fixed, is would be nice to stop ignoring the the latest tag to avoid those kind of problems.

Fixed in sinopia@0.8.0, now "latest" tag is treated like all other tags.

closing as duplicate of #50