{
  "name": "apollo-server-plugin-operation-registry",
  "version": "0.0.1-alpha.7",
  "description": "Apollo Server operation registry",
  "main": "dist/index.js",
  "types": "dist/index.d.ts",
  "keywords": [],
  "author": "Apollo <npm@apollographql.com>",
  "license": "Copyright (c) Meteor Development Group, Inc.; See LICENSE.md.",
  "engines": {
    "node": ">=6"
  },
  "dependencies": {
    "apollo-graphql": "0.1.0",
    "apollo-server-caching": "^0.3.1",
    "apollo-server-errors": "^2.2.0",
    "apollo-server-plugin-base": "^0.3.2",
    "fast-json-stable-stringify": "^2.0.0",
    "loglevel": "^1.6.1",
    "loglevel-debug": "^0.0.1",
    "node-fetch": "^2.3.0"
  },
  "peerDependencies": {
    "graphql": "^0.12.0 || ^0.13.0 || ^14.0.0"
  }
}

{
  "name": "apollo-server-plugin-operation-registry",
  "version": "0.0.1-alpha.7",
  "description": "Apollo Server operation registry",
  "main": "dist/index.js",
  "types": "dist/index.d.ts",
  "keywords": [],
  "author": "Apollo <npm@apollographql.com>",
  "license": "Copyright (c) Meteor Development Group, Inc.; See LICENSE.md.",
  "engines": {
    "node": ">=8"
  },
  "dependencies": {
    "apollo-graphql": "0.1.0",
    "apollo-server-caching": "^0.3.1",
    "apollo-server-errors": "^2.2.0",
    "apollo-server-plugin-base": "^0.3.2",
    "fast-json-stable-stringify": "^2.0.0",
    "loglevel": "^1.6.1",
    "loglevel-debug": "^0.0.1",
    "node-fetch": "^2.3.0"
  },
  "peerDependencies": {
    "graphql": "^0.12.0 || ^0.13.0 || ^14.0.0"
  }
}

Drop support for Node.js 6 and update TS compilation targets accordingly.
Drop support for Node.js 6 and update TS compilation targets accordingly.

This commit:

* Drops testing of Node.js 6.
* Updates the `engines` property of the affected packages to suggest using a
  newer version of Node.js (note this is only an attribute and not enforced
  by anything in the Node.js runtime).
* Changes the compilation target within TypeScript from ES2016 to ES2017.
  While Node.js 8 does not fully support ES2017, this compat table seems to
  suggest that it would be unlikely that we'd run into any problems by
  transpiling to ES2017's native features as I don't expect anything will
  make use of `SharedArrayBuffer`s or `Atomics`:

    * https://node.green/#ES2017
