npm-registry-fetch
Advanced tools
Comparing version 1.1.1 to 2.0.0
@@ -5,2 +5,17 @@ # Change Log | ||
<a name="2.0.0"></a> | ||
# [2.0.0](https://github.com/npm/registry-fetch/compare/v1.1.1...v2.0.0) (2018-04-08) | ||
### meta | ||
* drop support for node@4 ([758536e](https://github.com/npm/registry-fetch/commit/758536e)) | ||
### BREAKING CHANGES | ||
* node@4 is no longer supported | ||
<a name="1.1.1"></a> | ||
@@ -7,0 +22,0 @@ ## [1.1.1](https://github.com/npm/registry-fetch/compare/v1.1.0...v1.1.1) (2018-04-06) |
{ | ||
"name": "npm-registry-fetch", | ||
"version": "1.1.1", | ||
"version": "2.0.0", | ||
"description": "Fetch-based http client for use with npm registry APIs", | ||
@@ -5,0 +5,0 @@ "main": "index.js", |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Deprecated
MaintenanceThe maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.
Found 1 instance in 1 package
34456
0