Can't merge my types and resolvers using merge-graphql-schemas

help
1

I’m using Meteor to build a GraphQL server. I’m using the merge-graphql-schemas package to merge the schemas and resolvers from many file into one.

Meteor is crashing when I set it up as described the readme:

My structure is:

index.js
+-- graphql
|   +-- resolvers
|   |   +-- author.resolvers.js
|   |   +-- book.resolvers.js
|   |   +-- index.ts
|   +-- types
|   |   +-- typeA1.js
|   |   +-- typeA2.js
|   |   +-- typeB1.js
|   |   +-- typeB2.js
|   |   +-- index.js

Inside of the types/resolvers index file:

/resolvers/index.js

import path from 'path';
import mergeGraphqlSchemas from 'merge-graphql-schemas';

const fileLoader = mergeGraphqlSchemas.fileLoader
const mergeTypes = mergeGraphqlSchemas.mergeTypes

console.log(`types dirname: ${__dirname}`);
console.log(`types path: ${path.join(__dirname, '.')}`);

const typesArray = fileLoader(path.join(__dirname, '.'), { recursive: true })

export default mergeTypes(typesArray, { all: true })

with console output:

resolvers dirname: /graphql/resolvers
resolvers path: /graphql/resolvers

/types/index.js

import path from 'path';
import mergeGraphqlSchemas from 'merge-graphql-schemas';

const fileLoader = mergeGraphqlSchemas.fileLoader
const mergeTypes = mergeGraphqlSchemas.mergeTypes

const typesArray = fileLoader(path.join(__dirname, '.'), { recursive: true })

export default mergeTypes(typesArray, { all: true })

console output:

types dirname: /graphql/types
types path: /graphql/types

Could Meteor me messing with the paths here?

2

Could Meteor me messing with the paths here?

Probably. If you don’t put your code in an /imports directory or define your application entry points as per below from the Meteor 1.7 release then Meteor will follow the default load order rules, which you probably don’t want.

Applications may now specify client and server entry point modules in a newly-supported "meteor" section of
package.json:

"meteor": {
  "mainModule": {
    "client": "client/main.js",
    "server": "server/main.js"
  }
}

When specified, these entry points override Meteor's default module loading semantics, rendering imports
directories unnecessary. If mainModule is left unspecified for either client or server, the default rules will apply for
that architecture, as before. To disable eager loading of modules on a given architecture, simply provide a
mainModule value of false:

"meteor": {
  "mainModule": {
    "client": false,
    "server": "server/main.js"
  }
}