npm-registry-fetch - npm Package Compare versions

Comparing version 8.0.3 to 8.1.0

CHANGELOG.md

		@@ -5,2 +5,9 @@ # Changelog

		## [8.1.0](https://github.com/npm/registry-fetch/compare/v8.0.3...v8.1.0) (2020-05-20)


		### Features

		* add npm-command HTTP header ([1bb4eb2](https://github.com/npm/registry-fetch/commit/1bb4eb2c66ee8a0dc62558bdcff1b548e2bb9820))

		### [8.0.3](https://github.com/npm/registry-fetch/compare/v8.0.2...v8.0.3) (2020-05-13)
		@@ -7,0 +14,0 @@

index.js

		@@ -189,2 +189,6 @@ 'use strict'

		if (opts.npmCommand) {
		headers['npm-command'] = opts.npmCommand
		}

		const auth = getAuth(registry, opts)
		@@ -191,0 +195,0 @@ // If a tarball is hosted on a different place than the manifest, only send

package.json

		{
		"name": "npm-registry-fetch",
		"version": "8.0.3",
		"version": "8.1.0",
		"description": "Fetch-based http client for use with npm registry APIs",
		@@ -5,0 +5,0 @@ "main": "index.js",

README.md

		@@ -401,2 +401,11 @@ # npm-registry-fetch

		##### <a name="opts-npmCommand"></a> `opts.npmCommand`

		* Type: String
		* Default: null

		If provided, it will be sent in the `npm-command` header. This yeader is
		used by the npm registry to identify the npm command that caused this
		request to be made.

		##### <a name="opts-offline"></a> `opts.offline`
		@@ -403,0 +412,0 @@

New alerts