sfcode: npm-registry-fetch <a href="https://npm.im/npm-registry-fetch"><img src="https://img.shields.io/npm/v/npm-registry-fetch.svg" alt="npm version"/></a> <a href="https://npm.im/npm-registry-fetch"><img src="https://img.shields.io/npm/l/npm-registry-fetch.svg" alt="license"/></a> <a href="https://travis-ci.org/npm/npm-registry-fetch"><img src="https://img.shields.io/travis/npm/npm-registry-fetch/latest.svg" alt="Travis"/></a> <a href="https://ci.appveyor.com/project/npm/npm-registry-fetch"><img src="https://img.shields.io/appveyor/ci/zkat/npm-registry-fetch/latest.svg" alt="AppVeyor"/></a> <a href="https://coveralls.io/github/npm/npm-registry-fetch?branch=latest"><img src="https://coveralls.io/repos/github/npm/npm-registry-fetch/badge.svg?branch=latest" alt="Coverage Status"/></a>
npm-registry-fetch

`npm-registry-fetch` is a Node.js library that implements a `fetch`-like API for accessing npm registry APIs consistently. It's able to consume npm-style configuration values and has all the necessary logic for picking registries, handling scopes, and dealing with authentication details built-in.

This package is meant to replace the older `npm-registry-client`.

# Example

const npmFetch = require('npm-registry-fetch')
console.log(
await npmFetch.json('/-/ping')
)

# Table of Contents

- Installing
- Example
- Contributing
- API
  - `fetch`
  - `fetch.json`
  - `fetch` options

## Install

`$ npm install npm-registry-fetch`

## Contributing

The npm team enthusiastically welcomes contributions and project participation! There's a bunch of things you can do if you want to contribute! The ContributorGuide" has all the information you need for everything from reporting bugs to contributing entire new features. Please don't hesitate to jump in if you'd like to, or even ask us questions if something isn't clear.

All participants and maintainers in this project are expected to follow Code ofConduct", and just generally be excellent to each other.

Please refer to the Changelog for project history details, too.

Happy hacking!

## API

### Caching and <tt>write=true</tt> query strings

Before performing any PUT or DELETE operation, npm clients first make a GET request to the registry resource being updated, which includes the query string `?write=true`.

The semantics of this are, effectively, "I intend to write to this thing, and need to know the latest current value, so that my write can land cleanly".

The public npm registry handles these `?write=true` requests by ensuring that the cache is re-validated before sending a response. In order to maintain the same behavior on the client, and not get tripped up by an overeager local cache when we intend to write data to the registry, any request that comes through `npm-registry-fetch` that contains `write=true` in the query string will forcibly set the `prefer-online` option to `true`, and set both `prefer-offline` and `offline` to false, so that any local cached value will be revalidated.

### <a name="fetch"></a> <tt>> fetch(url, [opts]) -> Promise<Response></tt>

Performs a request to a given URL.

The URL can be either a full URL, or a path to one. The appropriate registry will be automatically picked if only a URL path is given.

For available options, please see the section on `fetch` options.

#### Example

const res = await fetch('/-/ping')
console.log(res.headers)
res.on('data', d => console.log(d.toString('utf8')))

### <a name="fetch-json"></a> <tt>> fetch.json(url, [opts]) -> Promise<ResponseJSON></tt>

Performs a request to a given registry URL, parses the body of the response as JSON, and returns it as its final value. This is a utility shorthand for `fetch(url).then(res => res.json())`.

For available options, please see the section on `fetch` options.

#### Example

const res = await fetch.json('/-/ping')
console.log(res) // Body parsed as JSON

### <a name="fetch-json-stream"></a> <tt>> fetch.json.stream(url, jsonPath, [opts]) -> Stream</tt>

Performs a request to a given registry URL and parses the body of the response as JSON, with each entry being emitted through the stream.

The `jsonPath` argument is a `JSONStream.parse()` path, and the returned stream (unlike default `JSONStream`s), has a valid `Symbol.asyncIterator` implementation.

For available options, please see the section on `fetch` options.

#### Example

console.log('https://npm.im/~zkat has access to the following packages:')
for await (let {key, value} of fetch.json.stream('/-/user/zkat/package', '$*')) {
console.log(`https://npm.im/${key} (perms: ${value})`)
}

### <a name="fetch-opts"></a> <tt>fetch</tt> Options

Fetch options are optional, and can be passed in as either a Map-like object (one with a `.get()` method), a plain javascript object, or a `figgy-pudding` instance.

#### <a name="opts-agent"></a> <tt>opts.agent</tt>

- Type: http.Agent
- Default: an appropriate agent based on URL protocol and proxy settings

An `Agent` instance to be shared across requests. This allows multiple concurrent `fetch` requests to happen on the same socket.

You do not need to provide this option unless you want something particularly specialized, since proxy configurations and http/https agents are already automatically managed internally when this option is not passed through.

#### <a name="opts-body"></a> <tt>opts.body</tt>

- Type: Buffer | Stream | Object
- Default: null

Request body to send through the outgoing request. Buffers and Streams will be passed through as-is, with a default `content-type` of `application/octet-stream`. Plain JavaScript objects will be `JSON.stringify`ed and the `content-type` will default to `application/json`.

Use `opts.headers` to set the content-type to something else.

#### <a name="opts-ca"></a> <tt>opts.ca</tt>

- Type: String, Array, or null
- Default: null

The Certificate Authority signing certificate that is trusted for SSL connections to the registry. Values should be in PEM format (Windows calls it "Base-64 encoded X.509 (.CER)") with newlines replaced by the string ‘’
'`. For example:

{
ca: '-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----'
}

Set to `null` to only allow "known" registrars, or to a specific CA cert to trust only that specific signing authority.

Multiple CAs can be trusted by specifying an array of certificates instead of a single string.

See also `opts.strict-ssl`, `opts.ca` and `opts.key`

#### <a name="opts-cache"></a> <tt>opts.cache</tt>

- Type: path
- Default: null

The location of the http cache directory. If provided, certain cachable requests will be cached according to IETF RFC 7234 rules. This will speed up future requests, as well as make the cached data available offline if necessary/requested.

See also `offline`, `prefer-offline`, and `prefer-online`.

#### <a name="opts-cert"></a> <tt>opts.cert</tt>

- Type: String
- Default: null

A client certificate to pass when accessing the registry. Values should be in PEM format (Windows calls it "Base-64 encoded X.509 (.CER)") with newlines replaced by the string ‘’
'`. For example:

{
cert: '-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----'
}

It is not the path to a certificate file (and there is no "certfile" option).

See also: `opts.ca` and `opts.key`

#### <a name="opts-fetch-retries"></a> <tt>opts.fetch-retries</tt>

- Type: Number
- Default: 2

The "retries" config for `retry` to use when fetching packages from the registry.

See also `opts.retry` to provide all retry options as a single object.

#### <a name="opts-fetch-retry-factor"></a> <tt>opts.fetch-retry-factor</tt>

- Type: Number
- Default: 10

The "factor" config for `retry` to use when fetching packages.

See also `opts.retry` to provide all retry options as a single object.

#### <a name="opts-fetch-retry-mintimeout"></a> <tt>opts.fetch-retry-mintimeout</tt>

- Type: Number
- Default: 10000 (10 seconds)

The "minTimeout" config for `retry` to use when fetching packages.

See also `opts.retry` to provide all retry options as a single object.

#### <a name="opts-fetch-retry-maxtimeout"></a> <tt>opts.fetch-retry-maxtimeout</tt>

- Type: Number
- Default: 60000 (1 minute)

The "maxTimeout" config for `retry` to use when fetching packages.

See also `opts.retry` to provide all retry options as a single object.

#### <a name="opts-force-auth"></a> <tt>opts.force-auth</tt>

- Alias: `opts.forceAuth`
- Type: Object
- Default: null

If present, other auth-related values in `opts` will be completely ignored, including `alwaysAuth`, `email`, and `otp`, when calculating auth for a request, and the auth details in `opts.forceAuth` will be used instead.

#### <a name="opts-gzip"></a> <tt>opts.gzip</tt>

- Type: Boolean
- Default: false

If true, `npm-registry-fetch` will set the `Content-Encoding` header to `gzip` and use `zlib.gzip()` or `zlib.createGzip()` to gzip-encode `opts.body`.

#### <a name="opts-headers"></a> <tt>opts.headers</tt>

- Type: Object
- Default: null

Additional headers for the outgoing request. This option can also be used to override headers automatically generated by `npm-registry-fetch`, such as `Content-Type`.

#### <a name="opts-ignore-body"></a> <tt>opts.ignore-body</tt>

- Alias: `opts.ignoreBody`
- Type: Boolean
- Default: false

If true, the response body will be thrown away and `res.body` set to `null`. This will prevent dangling response sockets for requests where you don't usually care what the response body is.

#### <a name="opts-integrity"></a> <tt>opts.integrity</tt>

- Type: String | SRI object
- Default: null

If provided, the response body's will be verified against this integrity string, using `ssri`. If verification succeeds, the response will complete as normal. If verification fails, the response body will error with an `EINTEGRITY` error.

Body integrity is only verified if the body is actually consumed to completion – that is, if you use `res.json()`/`res.buffer()`, or if you consume the default `res` stream data to its end.

Cached data will have its integrity automatically verified using the previously-generated integrity hash for the saved request information, so `EINTEGRITY` errors can happen if `opts.cache` is used, even if `opts.integrity` is not passed in.

#### <a name='opts-is-from-ci'></a> <tt>opts.is-from-ci</tt>

- Alias: `opts.isFromCI`
- Type: Boolean
- Default: Based on environment variables

This is used to populate the `npm-in-ci` request header sent to the registry.

#### <a name="opts-key"></a> <tt>opts.key</tt>

- Type: String
- Default: null

A client key to pass when accessing the registry. Values should be in PEM format with newlines replaced by the string ‘’
'`. For example:

{
key: '-----BEGIN PRIVATE KEY-----\nXXXX\nXXXX\n-----END PRIVATE KEY-----'
}

It is not the path to a key file (and there is no "keyfile" option).

See also: `opts.ca` and `opts.cert`

#### <a name="opts-local-address"></a> <tt>opts.local-address</tt>

- Type: IP Address String
- Default: null

The IP address of the local interface to use when making connections to the registry.

See also `opts.proxy`

#### <a name="opts-log"></a> <tt>opts.log</tt>

- Type: `npmlog`-like
- Default: null

Logger object to use for logging operation details. Must have the same methods as `npmlog`.

#### <a name="opts-map-json"></a> <tt>opts.map-json</tt>

- Alias: `mapJson`, `mapJSON`
- Type: Function
- Default: undefined

When using `fetch.json.stream()` (NOT `fetch.json()`), this will be passed down to `JSONStream` as the second argument to `JSONStream.parse`, and can be used to transform stream data before output.

#### <a name="opts-maxsockets"></a> <tt>opts.maxsockets</tt>

- Alias: `opts.max-sockets`
- Type: Integer
- Default: 12

Maximum number of sockets to keep open during requests. Has no effect if `opts.agent` is used.

#### <a name="opts-method"></a> <tt>opts.method</tt>

- Type: String
- Default: 'GET'

HTTP method to use for the outgoing request. Case-insensitive.

#### <a name="opts-noproxy"></a> <tt>opts.noproxy</tt>

- Type: Boolean
- Default: process.env.NOPROXY

If true, proxying will be disabled even if `opts.proxy` is used.

#### <a name="opts-npm-session"></a> <tt>opts.npm-session</tt>

- Alias: `opts.npmSession`
- Type: String
- Default: null

If provided, will be sent in the `npm-session` header. This header is used by the npm registry to identify individual user sessions (usually individual invocations of the CLI).

#### <a name="opts-offline"></a> <tt>opts.offline</tt>

- Type: Boolean
- Default: false

Force offline mode: no network requests will be done during install. To allow `npm-registry-fetch` to fill in missing cache data, see `opts.prefer-offline`.

This option is only really useful if you're also using `opts.cache`.

This option is set to `true` when the request includes `write=true` in the query string.

#### <a name="opts-otp"></a> <tt>opts.otp</tt>

- Type: Number | String
- Default: null

This is a one-time password from a two-factor authenticator. It is required for certain registry interactions when two-factor auth is enabled for a user account.

#### <a name="opts-password"></a> <tt>opts.password</tt>

- Alias: `_password`
- Type: String
- Default: null

Password used for basic authentication. For the more modern authentication method, please use the (more secure) `opts.token`

Can optionally be scoped to a registry by using a "nerf dart" for that registry. That is:

{
'//registry.npmjs.org/:password': 't0k3nH34r'
}

See also `opts.username`

#### <a name="opts-prefer-offline"></a> <tt>opts.prefer-offline</tt>

- Type: Boolean
- Default: false

If true, staleness checks for cached data will be bypassed, but missing data will be requested from the server. To force full offline mode, use `opts.offline`.

This option is generally only useful if you're also using `opts.cache`.

This option is set to `false` when the request includes `write=true` in the query string.

#### <a name="opts-prefer-online"></a> <tt>opts.prefer-online</tt>

- Type: Boolean
- Default: false

If true, staleness checks for cached data will be forced, making the CLI look for updates immediately even for fresh package data.

This option is generally only useful if you're also using `opts.cache`.

This option is set to `true` when the request includes `write=true` in the query string.

#### <a name="opts-project-scope"></a> <tt>opts.project-scope</tt>

- Alias: `opts.projectScope`
- Type: String
- Default: null

If provided, will be sent in the `npm-scope` header. This header is used by the npm registry to identify the toplevel package scope that a particular project installation is using.

#### <a name="opts-proxy"></a> <tt>opts.proxy</tt>

- Type: url
- Default: null

A proxy to use for outgoing http requests. If not passed in, the `HTTP(S)_PROXY` environment variable will be used.

#### <a name="opts-query"></a> <tt>opts.query</tt>

- Type: String | Object
- Default: null

If provided, the request URI will have a query string appended to it using this query. If `opts.query` is an object, it will be converted to a query string using `querystring.stringify()`.

If the request URI already has a query string, it will be merged with `opts.query`, preferring `opts.query` values.

#### <a name="opts-refer"></a> <tt>opts.refer</tt>

- Alias: `opts.referer`
- Type: String
- Default: null

Value to use for the `Referer` header. The npm CLI itself uses this to serialize the npm command line using the given request.

#### <a name="opts-registry"></a> <tt>opts.registry</tt>

- Type: URL
- Default: ‘'https://registry.npmjs.org&rsquo;`

Registry configuration for a request. If a request URL only includes the URL path, this registry setting will be prepended. This configuration is also used to determine authentication details, so even if the request URL references a completely different host, `opts.registry` will be used to find the auth details for that request.

See also `opts.scope`, `opts.spec`, and `opts.<scope>:registry` which can all affect the actual registry URL used by the outgoing request.

#### <a name="opts-retry"></a> <tt>opts.retry</tt>

- Type: Object
- Default: null

Single-object configuration for request retry settings. If passed in, will override individually-passed `fetch-retry-*` settings.

#### <a name="opts-scope"></a> <tt>opts.scope</tt>

- Type: String
- Default: null

Associate an operation with a scope for a scoped registry. This option can force lookup of scope-specific registries and authentication.

See also `opts.<scope>:registry` and `opts.spec` for interactions with this option.

#### <a name="opts-scope-registry"></a> <tt>opts.<scope>:registry</tt>

- Type: String
- Default: null

This option type can be used to configure the registry used for requests involving a particular scope. For example, ‘opts[’@myscope:registry'] = 'https://scope-specific.registry/'`will make it so requests go out to this registry instead of [`opts.registry<tt>](#opts-registry) when [opts.scope<tt>](#opts-scope) is used, or when [opts.spec`](#opts-spec) is a scoped package spec.

The `@` before the scope name is optional, but recommended.

#### <a name="opts-spec"></a> <tt>opts.spec</tt>

- Type: String | `npm-registry-arg` object.
- Default: null

If provided, can be used to automatically configure `opts.scope` based on a specific package name. Non-registry package specs will throw an error.

#### <a name="opts-strict-ssl"></a> <tt>opts.strict-ssl</tt>

- Type: Boolean
- Default: true

Whether or not to do SSL key validation when making requests to the registry via https.

See also `opts.ca`.

#### <a name="opts-timeout"></a> <tt>opts.timeout</tt>

- Type: Milliseconds
- Default: 0 (no timeout)

Time before a hanging request times out.

#### <a name="opts-token"></a> <tt>opts.token</tt>

- Alias: `opts._authToken`
- Type: String
- Default: null

Authentication token string.

Can be scoped to a registry by using a "nerf dart" for that registry. That is:

{
'//registry.npmjs.org/:token': 't0k3nH34r'
}

#### <a name="opts-user-agent"></a> <tt>opts.user-agent</tt>

- Type: String
- Default: ‘'npm-registry-fetch<version>/node<node-version>+<arch> (<platform>)’`

User agent string to send in the `User-Agent` header.

#### <a name="opts-username"></a> <tt>opts.username</tt>

- Type: String
- Default: null

Username used for basic authentication. For the more modern authentication method, please use the (more secure) `opts.token`

Can optionally be scoped to a registry by using a "nerf dart" for that registry. That is:

{
'//registry.npmjs.org/:username': 't0k3nH34r'
}

See also `opts.password`

#### <a name="opts-auth"></a> <tt>opts._auth</tt>

- Type: String
- Default: null

** DEPRECATED ** This is a legacy authentication token supported only for compatibility. Please use `opts.token` instead.