makeSchema's outputs/contextType .ts files need to be replaced with .js in production

In the tutorial here: https://nexusjs.org/docs/getting-started/tutorial/chapter-adding-mutations-to-your-api#wire-up-the-context

…the following example is given:

  outputs: {
    typegen: join(__dirname, '..', 'nexus-typegen.ts'),
    schema: join(__dirname, '..', 'schema.graphql')
  },
  contextType: {                                    // 1
    module: join(__dirname, "./context.ts"),        // 2
    export: "ContextModule",                        // 3
  },

When TypeScript files are compiled to JavaScript, references to nexus-typegen.ts and ./context.ts need to be replaced with nexus-typegen.js and ./context.js , otherwise those files won’t be found. Here’s a suggestion on what it can be changed to:

  const ext = process.env.NODE_ENV === 'production' ? 'js' : 'ts';

  outputs: {
    typegen: join(__dirname, '..', `nexus-typegen.${ext}`),
    schema: join(__dirname, '..', 'schema.graphql'),
  },
  contextType: {
    module: join(__dirname, `./context.${ext}`),
    export: 'Context',
  },

[miguelc1221]

ran into a similar issue, using tsc to compile and it can’t find the ./context.ts in the dist folder, my solution was to generate the typegen before compiling when in dev but still need the above solution @chrishoermann suggested. Dropping the extension doesn’t seem to work .......dist/src/api/context for the type context does not exist

[santialbo]

Nexus generates a typescript types file on development which should be compiled by typescript, there’s no need to change the extension on the output configuration. About the contextType, just drop the extension as you would do when you use import on your ts files.

  outputs: {
    typegen: join(__dirname, '..', `nexus-typegen.ts`),
    schema: join(__dirname, '..', 'schema.graphql'),
  },
  contextType: {
    module: join(__dirname, `./context`),
    export: 'Context',
  },