npmjs.org doesn't link to this repo

[wbeard]

Hi there,

Just thought I'd let you know that your wonderful module, as listed on npmjs.org, doesn't have its github repo linked.

You might want to look into this.

Thanks,

William Beard

[iarna]

Can you elaborate on what you were expecting? When I look at:

https://www.npmjs.com/package/artifactory-api

I see, on the right hand side in the column "One open issue on Github" which links here...

[iarna]

Clarification: You expect a link to here to appear below the version # and above the license?

[cgadam]

Rebecca,

Correct.. I'm expecting something like this:
[image: Imágenes integradas 1]

But instead in the module I'm mentioning (artifactory-api) I see:

[image: Imágenes integradas 2]

So I'm not sure at this point if this is a problem with my package.json or
the npm registry not creating this link automatically.

Christian -

2015-08-18 20:08 GMT-03:00 Rebecca Turner notifications@github.com:

Clarification: You expect a link to here to appear below the version # and
above the license?

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

[iarna]

Yeah, everything looks ok to me, in your package.json and what's in the registry. I gather that our support team will be following up with the appropriate folks tomorrow during our regular business hours.

[cgadam]

Ok, thank you @iarna !

[cgadam]

Looks like it's related to this npm issue:
https://github.com/npm/newww/issues/1172

[aredridel]

And https://github.com/npm/newww/issues/1173 has a proposed fix.

[aredridel]

Also: if you sent images with your comments with your expectations, they didn't make it on to the issue.

[cgadam]

Thanks for referencing the other issue as well @aredridel !
The comment was added automatically to the issue when I replied to the support agent via email. So I guess support agents at least got the screenshot. Anyway, it is exactly what she described.

[aredridel]

Excellent.

[iarna]

@cagadam: Who me? I didn't see those images either– I've only interacted with this issue via the web. (I'm not actually from support per se– just providing some cross team help. 😃)

[cgadam]

@iarna ! I got confused after receiving e-mails from this open issue and other e-mails I exchanged with npm support team which point me also to 1172. :) In any case, thanks for your collaboration!!

[cgadam]

It is working now :)