@jasonkuhrt is it not possible to use Nexus without --transpile-only? Im passing a function that takes a generic argument through context and the compiler complains with `Untyped function calls may not accept type arguments.`when I pass it type arguments. https://codesandbox.io/s/laughing-bhabha-zfo83?file=/src/nexus.ts:418-460

hi all

how can i user enum defined in schema.prisma in nexus mutation's args? many thanks

Help with running nexus + prisma-plugin in production …

👋 Hey guys.. Does "null free lists" also hold true for

t.model

? See https://nexusjs.org/docs/plugins/prisma/api#null-free-lists It mentions that it is for

t.crud

but not for

t.model

Hi, is nexus type gen not able to resolve types from declaration merging?

import type { PrismaClient } from "@prisma/client"
import type { FastifyRequest, FastifyReply } from "fastify"

export interface Context {
  request: FastifyRequest
  reply: FastifyReply
  prisma: PrismaClient
}

// index.d.ts
import type { User } from "@prisma/client"

declare module "fastify" {
  type PassportUser = User
}

3rd party lib types

Can anyone explain what causes the

makeSchema

method to execute during the build process?

Does nexus support union types? I need to return a list of objects that differ in structure but from a business standpoint they are conceptually the same. Is there an example?

Do most people set:

nonNullDefaults: {
    input: true,
    output: true,
  },

?

Seems like its the safer option

At least it would better match prisma

If you type

String

in the prisma schema its a nonNull by default but

String?

is nullable

When will the Nexusjs version compatible with Prisma 2.14.0 be released? I wanna stop seeing the warning that the Prisma version is incompatible.

"Nexus defaults to both inputs and outputs being nullable. This means by default your API is conservative in what it sends but flexible in what it accepts." (https://nexusjs.org/docs/guides/nullability#example-nullability-flipped-at-type-level)

How is the output "conservative" since results will be null | entity? Seems like

entity

is more conservative (when setting noNull output to true.

Finally got to migrate away from Nexus Framework (which is kind of sad though), but my build seems to fail because of missing type definitions, when using

ts-node

and

tsc

for build:reflection and build. If I run

ts-node-dev --transpile-only

before, it will succeed. I shouldn't have to do this during deployment. I can't find anything about this. Any idea how I can succeed with the build without a bunch of type errors?

What's the best way to bundle nexus using webpack?

What's the best way to guard a prisma-plugin field

t.model

to return null instead of throwing an error (like when I use

authorized

middleware)

I followed the tutorial on testing but as soon as I add a few more tests I am getting this error:

listen EADDRINUSE: address already in use :::4000

Any ideas?

What's the best way to create a federatedSchema with nexus?

name: 'Mutation',
  definition(t) {
    t.crud.createOneUser({ alias: 'signupUser' })
    t.crud.deleteOnePost()  //what is this?

    t.field('createDraft', {
      type: 'Post',
      args: {
        title: nonNull(stringArg()),
        content: stringArg(),
        authorEmail: nonNull(stringArg()),
      },

What's the purpose of

t.crud.deleteOnePost()

?

Is there a recommended method for handling authentication/authorization (preferably via the apollo context)? I need to get the request, pull header and do some checks.

Any idea why when I deploy my api, I get this error:

Cannot find module 'apollo-server-express'

It's not a problem, when I build and run locally. This is my tsconfig.json.

{
  "compilerOptions": {
    "skipLibCheck": true,
    "esModuleInterop": true,
    "target": "es2018",
    "module": "commonjs",
    "strict": false,
    "outDir": ".build",
    "rootDir": "."
  }
}

And my build/start script:

"build": "yarn build:reflection && yarn tsc",
    "build:reflection": "EXIT_AFTER_REFLECT=true ts-node --transpile-only ./app",
    "start": "NODE_ENV=production node .build/app",

I miss the framework already! 😄

Hi, is nexus-plugin-prisma still in active development? A long awaited crud feature described here https://github.com/graphql-nexus/nexus-plugin-prisma/issues/598 has been unpinned two weeks ago by @jasonkuhrt. Are you guys planned to continue this plugin development or just maintain it to match new prisma versions? In any cases i cant thank you enough for your amazing work.

Hi, maybe a silly question… but can I generate resolver by Nexus, and feed it and the SDL to the server?

And then take Nexus as a devdependency, which only for local dev and no need upload to the cloud.

In addition… I have seen strange error when using Nexus with apollo-server-lambda… If I wrote the graphql types and resolvers directly, I could query properly.

{
  "errorType": "TypeError",
  "errorMessage": "Symbol.prototype [ @@toPrimitive ] requires that 'this' be a Symbol",
  "stack": [
    "TypeError: Symbol.prototype [ @@toPrimitive ] requires that 'this' be a Symbol",
    "    at Symbol.[Symbol.toPrimitive] (<anonymous>)",
    "    at Function.defineProperty (<anonymous>)",
    "    at Object.<anonymous> (/var/task/__index.js:19:8)",
    "    at Module._compile (internal/modules/cjs/loader.js:999:30)",
    "    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)",
    "    at Module.load (internal/modules/cjs/loader.js:863:32)",
    "    at Function.Module._load (internal/modules/cjs/loader.js:708:14)",
    "    at Module.require (internal/modules/cjs/loader.js:887:19)",
    "    at require (internal/modules/cjs/helpers.js:74:18)",
    "    at _tryRequire (/var/runtime/UserFunction.js:75:12)"
  ]
}

Any idea?

If I want to split my resolver into a function like this:

t.field('event', { type: 'Event', resolve: eventResolver })

How would I then get proper type checking for the function:

const eventsResolver = async (root, args, ctx, ...rest) => {}

Assuming a complex graph, should the user create data node by node or should the user use a mutate request to create the entire document all once?