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

Develop an extensive Typescript and React shared library

The issue of Next.js redux useSelector causing HTML inconsistency

Does the routing in Angular 2 get disrupted by parameter breaks in sub-modules?

Issue encountered while executing jest tests - unable to read runtime.json file

Issues with APIs surfaced following the transition from DataGridPro to DataGridPremium

Using `this` within an object declaration

How to identify generic return type in TypeScript

Developing a Next.js shared library

Possibility for Automatic Type Inference in Generics

Exploring nested JSON objects within an array using ngFor directive

Steps for creating a copy of an Angular component

Developing a search feature using Angular 6 with Observable subscription for the FrontEnd application

Error: Unable to access $rootScope in the http interceptor response function

Getting a URL path in Next.js without relying on the Link component when the basePath is configured

Encountering an unexpected redirection issue with Google OAuth2 while using Node.js and Passport

The Importance of Strict Contextual Escaping in ReactJS

Top authentication approach for Ruby on Rails API-only server, paired with ActiveAdmin

What is the best way to retrieve an element that has been altered in its state?

Issue with the code: Only arrays and iterable objects are permitted in Angular 7

Challenge with concatenating Nextjs Links