零Rei

/cc @gozala

We should definitely do this! > _cough_ [`npm-registry-client`](https://github.com/npm/npm-registry-client/) _cough_ 📝 an issue plzthxomgbbq!

> Should the presence of a `LICENSE` always override the setting? That's the simplest and most intuitive thing to do. Explicit setting of the license in `package.json` trumps `LICENSE`, `LICENSE`...

To me, `1.2.3.4.5.6` and `1.2.3-4.5.6` are different in kind, and casting the former to SemVer implicitly feels like a stretch, even for loose mode. Having `node-semver` infer a prerelease tag...

Full disclosure: I was once employed by npm, Inc., and my duties included managing the CLI team, heading up community engagement with the CLI user base, and acting as a...

I have a couple brief responses to a few specific points you raise, and then I'll bow out of this discussion. > You seem defeated by the prospect of scaling...

It would be fantastic! Obviously! But the amount of git that npm uses is pretty hefty at this point. It's mostly `git clone`, `git status`, and `git tag` (with support...

> If they are so few commands, why npm doesn't use already a Javascript library? I bet @creationix would have a pithy answer to this; it turns out that supporting...

npm doesn't push upstream, but it does create commits, and GnuPG signs those commits, when creating new versions. Signed versions are one of the cornerstones of the npm release flow...

It's coming, probably sooner rather than later. It's figuring out where the boundaries are and coming up with a compatible way of shimming e.g. XHR that makes it tricky, but...