Build fails when building locally for production

[steinathan]

Nexus Report

{
 "node": "v13.6.0",
 "os": {
   "platform": "linux",
   "release": "5.3.0-40-generic"
 },
 "nexus": "^0.24.2",
 "plugins": [
   "nexus-plugin-prisma"
 ],
 "otherDependencies": {
   "axios": "^0.19.2",
   "bcryptjs": "^2.4.3",
   "cors": "^2.8.5",
   "cron": "^1.8.2",
   "date-fns": "^2.14.0",
   "graphql-shield": "^7.3.2",
   "jsonwebtoken": "^8.5.1"
 },
 "devDependencies": {
   "@types/bcryptjs": "^2.4.2",
   "@types/cors": "^2.8.6",
   "@types/jsonwebtoken": "^8.5.0"
 },
 "hasAppModule": true,
 "packageManager": "npm",
 "errorsWhileGatheringReport": {
   "gettingLayout": null,
   "gettingPluginManifests": null
 }
}

Description

Production build failed when trying to build the nexus for production, i had no errors when in development mode but as soon as i ran nexus build i got the following errors and build always fails on CI

> nexus build

1666 ● nexus:build get used plugins
1337 ○ app Started cronjobs at: 2020-06-28
  58 ○ app Started webhook service.. POST /webhook
 442 ● nexus:plugin:nexusPluginPrisma Running generators
1342 ● nexus:build starting reflection
s 18 ● nexus:build building typescript program
s 13 ● nexus:build compiling a production build
Error: node_modules/@types/typegen-nexus-context/index.d.ts:15:33 - error TS1109: Expression expected.

15 interface Context { me: User; } | { me?: undefined; }
                                   ~
node_modules/@types/typegen-nexus-context/index.d.ts:15:35 - error TS2363: The right-hand side of an arithmetic operation must be of type 'any', 'number', 'bigint' or an enum type.

15 interface Context { me: User; } | { me?: undefined; }
                                     ~~~~~~~~~~~~~~~~~~~
node_modules/@types/typegen-nexus-context/index.d.ts:15:51 - error TS1005: ',' expected.

15 interface Context { me: User; } | { me?: undefined; }
                                                     ~
node_modules/@types/typegen-nexus-prisma/index.d.ts:96:5 - error TS2300: Duplicate identifier 'contactDetails'.

96     contactDetails: 'ContactDetails'
       ~~~~~~~~~~~~~~
node_modules/@types/typegen-nexus-prisma/index.d.ts:97:5 - error TS2300: Duplicate identifier 'contactDetails'.

97     contactDetails: 'ContactDetails'
       ~~~~~~~~~~~~~~

    at Object.emitTSProgram (/home/navicstein/Aside/piggyGram/Servo/node_modules/nexus/dist/lib/tsc.js:67:15)
    at Object.buildNexusApp (/home/navicstein/Aside/piggyGram/Servo/node_modules/nexus/dist/lib/build/build.js:63:11)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Build.parse (/home/navicstein/Aside/piggyGram/Servo/node_modules/nexus/dist/cli/commands/build.js:33:9)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! dimegram@1.0.0 build: `nexus build`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the dimegram@1.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/navicstein/.npm/_logs/2020-06-28T20_50_57_937Z-debug.log

[steinathan]

Ive noticed that there's a bug in nexus-prisma plural table names, so i changed my table name from "ContactDetails" to "ContactDetail" and the error disappeared.

a little workaround to get the production build is to explicitly ignore/print errors instead of panicking for E.G in __dirname/node_modules/nexus/dist/lib/tsc.js:66

    if (allDiagnostics.length > 0) {
        console.error(ts.formatDiagnosticsWithColorAndContext(allDiagnostics, diagnosticHost));
    }

But.. am running a CI from gitlab to GAE and there's no way to pragmatically change the node_modules so i just added a little bash script to remove the line where nexus dies at typescript errors with

sed -i '67s/.*//' ./node_modules/nexus/dist/lib/tsc.js

i hope this works for me

But it will be a good thing if all interfaces are changed to types for example this throws errors somewhere

interface Context { me: User; } | { me?: undefined; } <-- The right-hand side of an arithmetic operation must be of type 'any', 'number', 'bigint' or an enum type.

but this works

type Context = { me: User; } | { me?: undefined; }```

[emyann]

@navicstein I think it's related to how union types are generated from addToContext returned type. I think I experienced the same issue here

[steinathan]

@emyann Meen, this is bursted, but am able to work around this culprit (for now) - wish they'll fix this ASAP

[Weakky]

Hey folks, this issue was closed by #1144. It will be available on the next preview release in a few minutes and on the next stable release soon as well.

Feel free to report problems on the issue despite it being closed if that didn't fix your problem.