Start errors out, GraphQL Syntax error

[benjamin-rood]

For each of the examples, getting GraphQLError: Syntax Error: Expected Name, found } after running npm install followed by npm start.

(node:51878) UnhandledPromiseRejectionWarning: GraphQLError: Syntax Error: Expected Name, found }
    at syntaxError (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/node_modules/graphql/error/syntaxError.js:24:10)
    at expect (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/node_modules/graphql/language/parser.js:1299:32)
    at parseName (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/node_modules/graphql/language/parser.js:92:15)
    at parseFieldDefinition (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/node_modules/graphql/language/parser.js:809:14)
    at many (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/node_modules/graphql/language/parser.js:1348:16)
    at parseFieldsDefinition (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/node_modules/graphql/language/parser.js:799:50)
    at parseObjectTypeDefinition (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/node_modules/graphql/language/parser.js:757:16)
    at parseTypeSystemDefinition (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/node_modules/graphql/language/parser.js:663:16)
    at parseDefinition (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/node_modules/graphql/language/parser.js:143:16)
    at parseDocument (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/node_modules/graphql/language/parser.js:110:22)
    at Object.parse (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/node_modules/graphql/language/parser.js:38:10)
    at Object.buildSchemaFromTypeDefinitions (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/node_modules/graphql-tools/dist/generate/buildSchemaFromTypeDefinitions.js:20:33)
    at Object.makeExecutableSchema (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/node_modules/graphql-tools/dist/makeExecutableSchema.js:27:29)
    at makeRemoteExecutableSchema (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/node_modules/graphql-tools/dist/stitching/makeRemoteExecutableSchema.js:134:35)
    at createUserSchema (/Users/br/Library/Mobile Documents/com~apple~CloudDocs/dev/tutorials/graphql/schema-stitching-examples/new-queries-mutations/index.js:30:10)
    at <anonymous>
(node:51878) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:51878) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

The unhandled promise error is a separate issue as far as I can tell.

System: macOS Version 10.13.6 (17G3025) Node Version: 9.4.0

I wonder if it's to do with a recent upstream node package upgrade?

[benjamin-rood]

Exception to the above:

• schema-transform example runs fine per README.
• basic-setup works if package-lock.json is removed prior to running npm install

[michaelhayman]

I get the same problem.