Wasp-lang•5mo ago

Getting an error trying to get an existing wasp app started

when I run wasp db migrate-dev on an existing wasp project I have NPM installed, it gives me this wrror [ Wasp ] auth/providers/types.ts(11,37): error TS2694: Namespace '"/Users/fatima/Downloads/app-main/node_modules/.prisma/client/index".Prisma' has no exported member 'UserCreateInput'. [ Wasp ] auth/utils.ts(131,17): error TS2694: Namespace '"/Users/fatima/Downloads/app-main/node_modules/.prisma/client/index".Prisma' has no exported member 'AuthWhereInput'. [ Wasp ] auth/utils.ts(192,27): error TS2339: Property 'PrismaClientKnownRequestError' does not exist on type 'typeof Prisma'. [ Wasp ] auth/utils.ts(192,62): error TS2339: Property 'code' does not exist on type 'unknown'. [ Wasp ] auth/utils.ts(198,27): error TS2339: Property 'PrismaClientValidationError' does not exist on type 'typeof Prisma'. [ Wasp ] auth/utils.ts(209,27): error TS2339: Property 'PrismaClientKnownRequestError' does not exist on type 'typeof Prisma'. [ Wasp ] auth/utils.ts(209,62): error TS2339: Property 'code' does not exist on type 'unknown'. [ Wasp ] auth/utils.ts(220,27): error TS2339: Property 'PrismaClientKnownRequestError' does not exist on type 'typeof Prisma'. [ Wasp ] auth/utils.ts(220,62): error TS2339: Property 'code' does not exist on type 'unknown'. [ Wasp ] entities/index.ts(2,8): error TS2305: Module '"@prisma/client"' has no exported member 'User'. [ Wasp ] entities/index.ts(3,8): error TS2305: Module '"@prisma/client"' has no exported member 'GptResponse'. [ Wasp ] entities/index.ts(4,8): error TS2305: Module '"@prisma/client"' has no exported member 'Task'. [ Wasp ] entities/index.ts(5,8): error TS2305: Module '"@prisma/client"' has no exported member 'File'. [ Wasp ] entities/index.ts(6,8): error TS2305: Module '"@prisma/client"' has no exported member 'ContactFormMessage'. [ Wasp ] entities/index.ts(7,8): error TS2305: Module '"@prisma/client"' h

17 Replies

kapa.ai•5mo ago

Hi @fatima. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- The error messages you're seeing indicate that the Prisma client is not recognizing the entities you've defined in your Wasp project. This could be due to a few reasons: 1. The Prisma client has not been generated yet. You can generate the Prisma client by running wasp db migrate-dev as mentioned in this issue (https://github.com/wasp-lang/wasp/issues/248). This command will generate the Prisma client and apply any pending migrations. 2. The entities are not defined correctly in your main.wasp file. Make sure that each entity is defined correctly, following the syntax shown in this issue (https://github.com/wasp-lang/wasp/issues/398). 3. There might be a version mismatch between Wasp and Prisma. Wasp has had issues with certain versions of Prisma in the past, as mentioned in this issue (https://github.com/wasp-lang/wasp/issues/158). Make sure you're using a compatible version of Prisma. If you're still having issues after checking these points, please provide more information about your Wasp and Prisma versions, and the content of your main.wasp file. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @fatima, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

fatimaOP•5mo ago

@kapa.ai This does not resolve the issue

kapa.ai•5mo ago

Let me check the knowledge base for you. One moment! :books: ---------------------- I'm sorry to hear that the issue persists. Without more specific information about your project setup, it's difficult to provide a more precise solution. However, here are a few more general steps you can try: 1. Reinstall Node Modules: Delete the node_modules folder and the package-lock.json file in your project directory. Then run npm install to reinstall your project dependencies. 2. Regenerate Prisma Client: Try regenerating the Prisma client by running npx prisma generate. 3. Check Entity Definitions: Make sure that the entities User, GptResponse, Task, File, and ContactFormMessage are correctly defined in your schema.prisma file. They should be defined as models like so:

model User {
  // fields
}

model GptResponse {
  // fields
}

// And so on for each entity...

model User {
  // fields
}

model GptResponse {
  // fields
}

// And so on for each entity...

4. Update Wasp: Ensure you're using the latest version of Wasp. You can update Wasp by running npm update -g wasp. If none of these steps solve your issue, I recommend creating a new issue in the Wasp Github repository (https://github.com/wasp-lang/wasp/issues) providing all the details about your setup and the problem you're facing. The Wasp team and community are quite responsive and should be able to help you out. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @fatima, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

fatimaOP•5mo ago

this is my main.wasp @kapa.ai

message.txt

kapa.ai•5mo ago

Let me check the knowledge base for you. One moment! :books: ---------------------- I'm sorry, but I can't provide the help you're looking for without more information. Could you please provide the content of your main.wasp file or describe the specific issue you're facing? ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @fatima, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

JLegendz•5mo ago

Hi Fatima, I don’t think the bot can access files, but I’ve copied and pasted my code directly with success before. Also, I’ll see if I can find it, but I asked a question awhile back about new entities not being recognized. It was because I had a ? on something that wasn’t supported. I’ll try to find the question. Here it is https://discord.com/channels/686873244791210014/1244099898912276531

Filip•5mo ago

Hey @fatima, can you maybe share the entire project so I can try to reproduce it? Thanks for the help @JLegendz!

fatimaOP•5mo ago

@sodic do you have a github email I can add to my repo? https://github.com/haarismian/app Thanks! @kapa.ai when I try npx prisma generate I get the following error We could not find your Prisma schema at

kapa.ai•5mo ago

Let me check the knowledge base for you. One moment! :books: ---------------------- The error message you're seeing indicates that the Prisma CLI is unable to locate your schema.prisma file. This file is typically located in the db directory of your Wasp project. Here are a few steps you can take to resolve this issue: 1. Check the location of your schema.prisma file: Ensure that the schema.prisma file is located in the db directory of your Wasp project. 2. Specify the schema path: When running the npx prisma generate command, you can specify the path to your schema.prisma file using the --schema option. For example, if your schema.prisma file is located in the db directory, you would run npx prisma generate --schema=./db/schema.prisma. 3. Check your working directory: Ensure that you're running the npx prisma generate command from the root directory of your Wasp project. If you're in a different directory, the Prisma CLI may not be able to locate your schema.prisma file. If you're still having issues after trying these steps, please provide more information about your project setup, such as the structure of your project directories and the content of your schema.prisma file. This will help in providing a more specific solution to your problem. For more information on how to work with Prisma in a Wasp project, you can refer to this issue (https://github.com/wasp-lang/wasp/issues/122) and this issue (https://github.com/wasp-lang/wasp/issues/427) from the Wasp Github repository. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

fatimaOP•5mo ago

@kapa.ai now I am getting this error: [ Server ] > [email protected] watch [ Server ] > nodemon --exec 'npm run bundle-and-start || exit 1' [ Server ] [ Client ] > [email protected] start [ Client ] > npm run validate-env && vite [ Client ] [ Server!] sh: nodemon: command not found

kapa.ai•5mo ago

Let me check the knowledge base for you. One moment! :books:

MEE6•5mo ago

Wohooo @fatima, you just became a Waspeteer level 1!

kapa.ai•5mo ago

---------------------- The error message you're seeing indicates that nodemon is not found, which means it's likely not installed in your project. nodemon is a utility that monitors for any changes in your source and automatically restarts your server. It's used in the development environment. Here's how you can install it: 1. Install nodemon locally in your project: Run npm install nodemon in the root directory of your project. 2. Install nodemon globally: If you want to use nodemon for other projects as well, you can install it globally by running npm install -g nodemon. After installing nodemon, try running your Wasp project again with wasp start. If you're still having issues, please provide more information about your project setup, such as the content of your package.json file. This will help in providing a more specific solution to your problem. For more information on how to work with Wasp and Node.js, you can refer to this issue (https://github.com/wasp-lang/wasp/issues/62) from the Wasp Github repository. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @fatima, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

fatimaOP•5mo ago

@kapa.ai - Error: Dependency conflict for user dependency (nodemon, ^3.1.4): Version must be set to the exactly the same version as the one wasp is using: ^2.0.19

kapa.ai•5mo ago

Let me check the knowledge base for you. One moment! :books: ---------------------- The error message you're seeing indicates that there's a version conflict between the nodemon package you're trying to use (^3.1.4) and the version that Wasp is using (^2.0.19). In the current version of Wasp, if Wasp is already internally using a certain dependency with a certain version specified, you are not allowed to define that same npm dependency yourself while specifying a different version. If you do that, you will get an error message telling you which exact version you have to use for that dependency. This means Wasp dictates exact versions of certain packages, so for example you can't choose the version of nodemon you want to use. To resolve this issue, you should set the version of nodemon in your package.json file to ^2.0.19, which is the version that Wasp is using. You can do this by running npm install nodemon@^2.0.19. For more information on how Wasp handles dependencies, you can refer to this issue (https://github.com/wasp-lang/wasp/issues/59) and this documentation (https://wasp-lang.dev/docs/project/dependencies) from the Wasp Github repository. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @fatima, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

fatimaOP•5mo ago

@sodic I figured it out, I needed to generate the prisma client but needed to specify where it was, which I didn't understand until now, thank you

Filip•5mo ago

Hey @fatima, sorry for the delay. I was out for the weekend. Glad you got it working! Could you explain in more detail what happened? Also, if you need to add me to a GitHub project, you can do so with my GH profile. It's "sodic"

Gaming

Programming

Getting an error trying to get an existing wasp app started