Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Feb 13, 2015
  1. Forrest L Norvell

    6.1.1

    othiym23 authored
  2. Forrest L Norvell

    fix typo

    othiym23 authored
  3. Forrest L Norvell

    6.1.0

    othiym23 authored
  4. Forrest L Norvell
  5. Forrest L Norvell
Commits on Feb 7, 2015
  1. Forrest L Norvell
Commits on Jan 30, 2015
  1. Forrest L Norvell

    6.0.7

    othiym23 authored
  2. Forrest L Norvell
  3. Forrest L Norvell

    6.0.6

    othiym23 authored
  4. Forrest L Norvell

    that colon is important

    othiym23 authored
  5. Forrest L Norvell

    6.0.5

    othiym23 authored
  6. Forrest L Norvell

    style tweaks

    othiym23 authored
  7. Forrest L Norvell

    add some shady ternary logic business

    othiym23 authored
    It's common for corporate network ops to interpose a proxy between
    developers running on the intranet and the big bad public internet. Many
    command-line HTTP clients, like cURL and wget, will use the PROXY and
    HTTPS_PROXY environment variables to figure out there's a proxy in
    action, and where it is. request, used by npm-registry-client,
    also follows this convention when no proxy configuration is passed to it
    with a request.
    
    It's also common for corporate networks to have intranet or DMZ hosts to
    which access should not be proxied. The aforementioned command-line
    utilities will read a comma-delimited, semi-globbed list of these hosts
    from the NOPROXY environment variable. request also gained the ability
    to use this configuration in the not too distant past. It also relies
    upon no proxy information being passed to request -- even if there is
    an object property set to `null`.
    
    But what if you want to override proxy settings at the command line?
    Before this change, there was no way to communicate to
    npm-registry-client that it should tell request not to read the proxy
    configuration from the environment. To get that information into
    npm-registry-client, it now looks for the HTTP proxy to be set to false.
    How the npm CLI gets that information to the client is a bit of movie
    magic that doesn't bear overly close examination (it relies heavily on
    the near-abuse of nopt's flexibility), but it does the trick.
    
    Also include some tests, because this corner of the client is pretty
    terribly underspecified and underdocumented. Let's hope there aren't too
    many more of these edge cases lurking about.
  8. Forrest L Norvell

    set options on both agent and `request` (fix #98)

    othiym23 authored
    * ensure keep-alive is enabled
    * create agent lazily
    * only create one HTTP agent and one HTTPS agent
    * only pass HTTPS parameters to HTTPS agent
Commits on Jan 29, 2015
  1. Forrest L Norvell

    6.0.4

    othiym23 authored
  2. Forrest L Norvell
Commits on Jan 24, 2015
  1. Forrest L Norvell

    6.0.3

    othiym23 authored
  2. Forrest L Norvell
  3. Forrest L Norvell

    6.0.2

    othiym23 authored
  4. Forrest L Norvell
Commits on Jan 23, 2015
  1. Forrest L Norvell

    6.0.1

    othiym23 authored
  2. Forrest L Norvell

    6.0.0

    othiym23 authored
  3. Forrest L Norvell

    access is a top-level property on publishes

    othiym23 authored
    This is a registry-2 feature, and is a breaking change, because it's not
    safe to choose a default value, because restricted publishes make no
    sense for unscoped packages, but public publishes can leak information
    for scoped packages.
  4. Forrest L Norvell

    5.1.0

    othiym23 authored
  5. Forrest L Norvell

    distTags methods (w/client bootstrapping update)

    othiym23 authored othiym23 committed
    Depends on `npm-package-arg` to only escape slashes in scoped package
    names. The additional level of indirection between the registry client
    prototype and the distTags methods necessitated some prototype chain
    hackery I'm none too proud of, but it's documented and works. The client
    is due for another rewrite anyway.
  6. Forrest L Norvell

    support for the package access endpoint

    othiym23 authored othiym23 committed
Commits on Jan 22, 2015
  1. Forrest L Norvell

    minor tag cleanup

    othiym23 authored
Commits on Jan 16, 2015
  1. Forrest L Norvell

    5.0.0

    othiym23 authored
  2. Forrest L Norvell
Commits on Dec 12, 2014
  1. Forrest L Norvell

    4.0.5

    othiym23 authored
Commits on Nov 22, 2014
  1. Forrest L Norvell

    4.0.4

    othiym23 authored
  2. Forrest L Norvell
  3. Forrest L Norvell

    less funky formatting

    othiym23 authored
  4. Forrest L Norvell
  5. Forrest L Norvell
Something went wrong with that request. Please try again.