2018-06-21 22:54:53 +02:00
|
|
|
{
|
|
|
|
|
"name": "apollo-server-lambda",
|
2018-09-18 15:26:48 -07:00
|
|
|
"version": "2.1.0",
|
2018-06-21 22:54:53 +02:00
|
|
|
"description": "Production-ready Node.js GraphQL server for AWS Lambda",
|
|
|
|
|
"keywords": [
|
|
|
|
|
"GraphQL",
|
|
|
|
|
"Apollo",
|
|
|
|
|
"Server",
|
|
|
|
|
"Lambda",
|
|
|
|
|
"Javascript"
|
|
|
|
|
],
|
|
|
|
|
"author": "opensource@apollographql.com",
|
|
|
|
|
"license": "MIT",
|
|
|
|
|
"repository": {
|
|
|
|
|
"type": "git",
|
|
|
|
|
"url": "https://github.com/apollographql/apollo-server/tree/master/packages/apollo-server-lambda"
|
|
|
|
|
},
|
|
|
|
|
"homepage": "https://github.com/apollographql/apollo-server#readme",
|
|
|
|
|
"bugs": {
|
|
|
|
|
"url": "https://github.com/apollographql/apollo-server/issues"
|
|
|
|
|
},
|
|
|
|
|
"main": "dist/index.js",
|
|
|
|
|
"types": "dist/index.d.ts",
|
|
|
|
|
"engines": {
|
|
|
|
|
"node": ">=6"
|
|
|
|
|
},
|
|
|
|
|
"dependencies": {
|
2018-06-29 13:56:38 +02:00
|
|
|
"@apollographql/graphql-playground-html": "^1.6.0",
|
2018-08-10 23:41:21 +02:00
|
|
|
"apollo-server-core": "file:../apollo-server-core",
|
|
|
|
|
"apollo-server-env": "file:../apollo-server-env",
|
Revert #1698 renovate/graphql tools 4.x (#1716)
I'm reverting apollographql/apollo-server#1698 not because it's been problematic in any way, but because I'd like to give it a bit more thought and don't want this to accidentally get cut into a release prior to that consideration.
More specifically: The `graphql-tools` update on its own shouldn't really cause any problems, but the [4.x version of `graphql-tools`](https://github.com/apollographql/graphql-tools/releases/tag/4.0.0) is intended to support and enable the latest `graphql@14` which contains [breaking changes](https://github.com/graphql/graphql-js/releases/tag/v14.0.0).
I believe most of those breaking changes would be show-stoppers and the failures would surface immediately (meaning that servers would completely fail to start, rather than being a surprise in other, more delayed scenarios), but it's still worth pausing and carefully considering versioning to avoid any surprises.
That said, the 14.x version of `graphql` has been an acceptable range in the `peerDependencies` of `apollo-server-*` since before its final release came out, and I don't believe we've caught wind of anything that a major version bump would have prevented or made more clear. In the end, `graphql` is a peer dependency and any problems should only surface if consumers also update their `graphql` dependency — a clear major version bump, which deserves review by the upgrader — so perhaps we can avoid bumping the major version after all?
Input welcomed, but again, merging this now to give this a bit more thought first.
cc @hwillson
2018-09-24 20:47:18 +03:00
|
|
|
"graphql-tools": "^3.0.4"
|
2018-06-21 22:54:53 +02:00
|
|
|
},
|
2018-09-03 14:42:05 +02:00
|
|
|
"devDependencies": {
|
|
|
|
|
"apollo-server-integration-testsuite": "file:../apollo-server-integration-testsuite"
|
|
|
|
|
},
|
2018-06-22 19:55:08 -03:00
|
|
|
"peerDependencies": {
|
|
|
|
|
"graphql": "^0.12.0 || ^0.13.0 || ^14.0.0"
|
2018-06-21 22:54:53 +02:00
|
|
|
}
|
|
|
|
|
}
|