This repository was archived by the owner on Aug 11, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 108
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: npm/npm-registry-client
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 0b595c4769f314a12661d537a328cf4e5658a00f
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: npm/npm-registry-client
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: debec76884db8092c2c7a21ab5b4ed083f8ce2c9
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 9 commits
- 11 files changed
- 3 contributors
Commits on Sep 3, 2016
-
Configuration menu - View commit details
-
Copy full SHA for f11a002 - Browse repository at this point
Copy the full SHA f11a002View commit details -
Configuration menu - View commit details
-
Copy full SHA for 04f418a - Browse repository at this point
Copy the full SHA 04f418aView commit details -
remove socket
error
handler after request is done`npm-registry-client` uses `request`, which in turn uses an HTTP agent for reusing sockets, so the `error` handlers registered on it in `npm-registry-client` just piled up and kept being attached over the entire lifetime of the socket. This patch seeks to fix this by removing the listener from the socket once the callback is invoked, as keeping it around after that would just be a memory leak.
Configuration menu - View commit details
-
Copy full SHA for 0ff3352 - Browse repository at this point
Copy the full SHA 0ff3352View commit details -
Configuration menu - View commit details
-
Copy full SHA for df9be53 - Browse repository at this point
Copy the full SHA df9be53View commit details -
Configuration menu - View commit details
-
Copy full SHA for f62a28d - Browse repository at this point
Copy the full SHA f62a28dView commit details -
Configuration menu - View commit details
-
Copy full SHA for cd23cfb - Browse repository at this point
Copy the full SHA cd23cfbView commit details -
The new nock wouldn't work if we still had to support Node.js 0.8, but since the CLI team has dropped support for 0.8, this isn't a problem.
Configuration menu - View commit details
-
Copy full SHA for 8331ef7 - Browse repository at this point
Copy the full SHA 8331ef7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 90113c9 - Browse repository at this point
Copy the full SHA 90113c9View commit details -
Configuration menu - View commit details
-
Copy full SHA for debec76 - Browse repository at this point
Copy the full SHA debec76View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 0b595c4769f314a12661d537a328cf4e5658a00f...debec76884db8092c2c7a21ab5b4ed083f8ce2c9