Gar
@lukekarrys I checked again and we do not use this attribute.
The config contained in the package.json is considered part of the version you are installing. It's intentionally coupled to that version's package.json. This is by design.
Can we get a test for this? You'll also need to rebase to the latest `main` to resolve conflicts
Fixing this here fixes auto esm exports for the most highly downloaded package on the entire npm registry. Fixing the lexer is outside the scope of what node-semver needs to...
```sh ~/D/n/ini (main|✔) $ npm view ini repository { type: 'git', url: 'git+https://github.com/npm/ini.git' } ```
I don't think this will make a difference either way, you're just changing how the stream is consumed. We think the real memory hog here is https://github.com/npm/cacache/blob/e3a2928e053e19fb6e8e73946ffe3d212e402ba7/lib/content/read.js#L11, and have plans...
If I go to a gitlab repo and find the archive url it's formatted like this `https://gitlab.com/gitlab-org/gitlab-foss/-/archive/master/gitlab-foss-master.tar.gz`, which works without authorization (as i would expect because it's public) If I...
The comment above that block kind of describes why we have only a subset there. It could probably be more elaborate. The `age` header for instance is one that if...
I think having a way to add additional headers makes sense, but also worry about the opaqueness of the current approach, which is a remnant of the provenance of this...
The alternative is that we simply add `Link` to that hard coded list. It's certainly not the most scalable solution (we have to make this decision every time there's a...