Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DEBUG logs in prisma-client after update plugin to 0.10.0 #1088

Closed
gustawdaniel opened this issue Jun 22, 2020 · 3 comments
Closed

DEBUG logs in prisma-client after update plugin to 0.10.0 #1088

gustawdaniel opened this issue Jun 22, 2020 · 3 comments

Comments

@gustawdaniel
Copy link

gustawdaniel commented Jun 22, 2020

When I updated to next version

    "nexus-plugin-prisma": "^0.10.0",

I see debug logs without DEBUG flag.

Nexus Report

This

1190 ▲ nexus:tsconfig Please set `compilerOptions.typeRoots` to ["node_modules/@types","types"]. "node_modules/@types" is the TypeScript default for types packages and where Nexus outputs typegen to. "types" is the Nexus convention for _local_ types packages.
   2 ▲ nexus:tsconfig Please add "types.d.ts" to your "include" array. If you do not then results from Nexus and your IDE will not agree if the declaration file is used in your project.
   0 ▲ nexus:tsconfig Please set `compilerOptions.noEmit` to true. This will ensure you do not accidentally emit using `$ tsc`. Use `$ nexus build` to build your app and emit JavaScript.

And this

{
  "node": "v12.14.1",
  "os": {
    "platform": "linux",
    "release": "5.3.0-59-generic"
  },
  "nexus": "^0.24.2",
  "plugins": [
    "nexus-plugin-prisma"
  ],
  "otherDependencies": {
    "@google-cloud/storage": "^5.1.1",
    "@google-cloud/vision": "^2.1.0",
    "@sendgrid/mail": "^7.2.0",
    "approx-string-match": "^1.1.0",
    "aws-sdk": "^2.701.0",
    "canvas": "^2.6.1",
    "chai-arrays": "^2.2.0",
    "chai-string": "^1.5.0",
    "cors": "^2.8.5",
    "dotenv": "^8.2.0",
    "node-pdftk": "git+https://git@github.com/gustawdaniel/node-pdftk.git",
    "pdf-image": "^2.0.0",
    "pdfjs-dist": "^2.4.456",
    "rsmq-worker": "^0.5.2",
    "uid": "^1.0.0"
  },
  "devDependencies": {
    "@babel/preset-env": "^7.10.3",
    "@prisma/cli": "^2.0.1",
    "@types/chai": "^4.2.11",
    "@types/mocha": "^7.0.2",
    "@types/node": "^14.0.13",
    "axios": "^0.19.2",
    "babel-jest": "^26.0.1",
    "chai": "^4.2.0",
    "chai-files": "^1.4.0",
    "mocha": "^8.0.1",
    "nyc": "^15.1.0",
    "prettier": "^2.0.5",
    "ts-node": "^8.10.2",
    "typescript": "^3.9.5"
  },
  "hasAppModule": true,
  "packageManager": "npm",
  "errorsWhileGatheringReport": {
    "gettingLayout": null,
    "gettingPluginManifests": null
  }
}

Screenshot

Zrzut ekranu z 2020-06-22 17-54-23

Description

I do not want to see yellow prisma-client DEBUG logs

I can't fix it using

https://www.nexusjs.org/#/api/modules/main/exports/settings?id=change

@danielmahon
Copy link

@gustawdaniel this was an issue (prisma/prisma#2787) in the upstream prisma client which was fixed in 2.1.0. It should be fixed here too once nexus-prisma-plugin updates to use 2.1.0. You can just delete process.env.DEBUG; for the time being if you want to disable it.

@danielmahon
Copy link

@gustawdaniel This is fixed now in the latest nexus-prisma-plugin release

@jasonkuhrt
Copy link
Member

Yep thanks @danielmahon! By graphql-nexus/nexus-plugin-prisma#733.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants