Rebecca Turner

It's pretty important that `npm` not have to select different tarballs based on syntax mode and here's why: Updating the cli to support new registry semantics and updating the npm...

Any time I think about es6 modules I get uncomfortable feelings around forward compatibility for published modules. The current status quo, which is that you write your modules in whatever...

As an aside: npm's support guarantees are broader than Node.js'. Currently npm only supports two major releases of npm itself. But it supports using them on versions of node going...

> 32bit and 64bit packages that are distributed in linux package managers There's nothing intrinsically wrong with that, but pushing it into an already established ecosystem feels untenable to me....

(None of this is to even speak about all-in-one-file packages, which are just JS files with the package.json embedded in the top. But I would be very happy to call...

Thank you for writing up such a detailed discussion of your needs. This is a use-case that we've discussed regarding 2fa internally at npm, and its one that we intend...

~~I would also note that the problematic rewriting behavior only happens with scoped modules. IMO at the VERY least it should not have different behaviors for scoped and unscoped modules.~~...

`files` and `.npmignore` behavior is surprisingly complicated and awful. 😭 The closest thing we have to comprehensive documentation is the [files and ignores test](https://github.com/npm/npm/blob/d46015256941ddfff1463338e3e2f8f77624a1ff/test/tap/files-and-ignores.js) that @zkat wrote the last time...

I intend to loop back on this one soonish and see if the repro is still an issue with some of the latest fixes (particularly those that fix filehandle leaks,...

I'd like to see https://github.com/npm/validate-npm-package-name/issues/1 addressed before we do the npm-registry-client changes, as I'd prefer to not change its semantics.