When TypeScript error "ts(18004)" occurs, it is because of the object properties within all Prisma DB

Question

When TypeScript error "ts(18004)" occurs, it is because of the object properties within all Prisma DB

I am currently in the process of verifying if a user's email already exists. To achieve this, I am utilizing Prisma Client's findUnique method. Below is the code snippet I have implemented:

const userWithEmail = await prisma.user.findUnique({
    where: {
      email,
    },
  });

However, I encountered a TypeScript error:

No value exists in scope for the shorthand property 'email'. Either declare one or provide an initializer.ts(18004)

Here is my schema.prisma file:

// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema
...

And here is my route.ts file:

import { PrismaClient } from "@prisma/client";
import { NextResponse } from "next/server";
import validator from "validator";
...

I am working with Next.js 13 and Prisma. Can someone please help me identify what I might be doing incorrectly?

typescript next.js prisma

Answer 1

Answer №1

It seems like the problem lies in this section:

const body = await request.json();

There is no method request.json(). If you had utilized

import { NextApiRequest } from "next";

TypeScript would have alerted you to this mistake. You should be using NextApiRequest

export interface NextApiRequest extends IncomingMessage {
  query: Partial<{
      [key: string]: string | string[];
  }>;
  cookies: Partial<{
      [key: string]: string;
  }>;
  body: any;
  env: Env;
  preview?: boolean;
  previewData?: PreviewData;
}

Although it extends IncomingMessage, it does not contain a json() property. Instead, you should do

const { email, password } = req.body;

Answer 2

It seems like the problem lies in this section:

const body = await request.json();

There is no method request.json(). If you had utilized

import { NextApiRequest } from "next";

TypeScript would have alerted you to this mistake. You should be using NextApiRequest

export interface NextApiRequest extends IncomingMessage {
  query: Partial<{
      [key: string]: string | string[];
  }>;
  cookies: Partial<{
      [key: string]: string;
  }>;
  body: any;
  env: Env;
  preview?: boolean;
  previewData?: PreviewData;
}

Although it extends IncomingMessage, it does not contain a json() property. Instead, you should do

const { email, password } = req.body;

Answer 3

Answer №2

Perhaps the "email" variant is not within the same scope in the method.
For example, if you declare the "email" variant before the findUnique call, this issue will be resolved.

const email = "<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="661203151226031e070b160a034805090b">[email protected]</a>"
const userWithEmail = await prisma.user.findUnique({
    where: {
      email,
    },
  });

If you do not declare the email variant as "email" (for example, name it mailAddress), try using the following code.

const mailAddress = "<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="e296879196a2879a838f928e87cc818d8d8f">[email protected]</a>"
const userWithEmail = await prisma.user.findUnique({
    where: {
      email: mailAddress,
    },
  });

Answer 4

Perhaps the "email" variant is not within the same scope in the method.
For example, if you declare the "email" variant before the findUnique call, this issue will be resolved.

const email = "<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="661203151226031e070b160a034805090b">[email protected]</a>"
const userWithEmail = await prisma.user.findUnique({
    where: {
      email,
    },
  });

If you do not declare the email variant as "email" (for example, name it mailAddress), try using the following code.

const mailAddress = "<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="e296879196a2879a838f928e87cc818d8d8f">[email protected]</a>"
const userWithEmail = await prisma.user.findUnique({
    where: {
      email: mailAddress,
    },
  });

When TypeScript error "ts(18004)" occurs, it is because of the object properties within all Prisma DB

Answer №1

Answer №2

Similar questions

Creating an object type that accommodates the properties of all union type objects, while the values are intersections, involves a unique approach

Successfully resolving the API without encountering any response errors, even after sending a response

"Encountering issues with Firebase deployment related to function-builder and handle-builder while working with TypeScript

I continue to encounter the same error while attempting to deliver data to this form

Using Angular2 - How to pass the router parameter as a variable in ngForm

Using Rxjs to dynamically map values from an array with forkJoin

Reactfire encounters import error in Next.js/React application leading to failure

Asynchronous jQuery operations using promises and finally functionality

There seems to be an issue with the TypeScript error: it does not recognize the property on the options

Unlock the full potential of Next.js 13 with Supabase: Discover the best practices for setting up a user context in your application

searchByTextContentUnderListItemAnchorTag

Angular2: Unable to locate the 'environment' namespace

TS2688 Error: TypeScript Build Fails to Locate Type Definition File for 'mocha' Following Update

"Error message: Antd datepicker is throwing an error stating that date.clone/date.load is not a

Arranging information by utilizing arrays

Optimizing TypeScript/JavaScript for both browser and Node environments through efficient tree-shaking

Angular firing off select option with object properties

Is it recommended to exclude the NGXS NgxsLoggerPluginModule for production deployments?

Implementing NestJS: Integrating TypeORM Datasource without relying on class dependency injection

I'm having trouble resolving this issue with an Unexpected Application Error! It seems that I cannot set the property value of #<TextFieldBase2> since it only has a