When I first ran Sinopia under node 0.10.33 / npm 1.4.7 I had little trouble getting Sinopia up and running, caching files from npmjs and serving locally published files.
We have upgraded and are using node 0.12.2 and npm 2.7.4, and I notice that Sinopia's package links say "By:" with no name. I have detected that the "_npmUser" field in package.json was populated in the older node/npm, but is not being populated with the new node/npm. After spending lots of time with my setup scripts, I rolled node back and publishing usernames reappeared.
NPM adduser tokens are being stored in the project .npmrc.
I did see another bug about "AUTH:Tokens" (#180) not being related; I suspect that might be a related issue (or the same, or a root cause); but from the workaround posts it looks like it is expected that behavior is already fixed (in npm 2.1.7); but I'm not seeing the publishing usernames as late as npm 2.7.4.
When I first ran Sinopia under node 0.10.33 / npm 1.4.7 I had little trouble getting Sinopia up and running, caching files from npmjs and serving locally published files.
We have upgraded and are using node 0.12.2 and npm 2.7.4, and I notice that Sinopia's package links say "By:" with no name. I have detected that the "_npmUser" field in package.json was populated in the older node/npm, but is not being populated with the new node/npm. After spending lots of time with my setup scripts, I rolled node back and publishing usernames reappeared.
NPM adduser tokens are being stored in the project .npmrc.
I did see another bug about "AUTH:Tokens" (#180) not being related; I suspect that might be a related issue (or the same, or a root cause); but from the workaround posts it looks like it is expected that behavior is already fixed (in npm 2.1.7); but I'm not seeing the publishing usernames as late as npm 2.7.4.
My sinopia version is 1.2.2.