wasp app wont start

I got on today and did wasp start today in my WSL console and now im getting this error.. anyone have any ideas?

28 Replies

MEE6•2mo ago

Wohooo @Anddy, you just became a Waspeteer level 2!

Hi @Anddy. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- I'm sorry, but without more specific information about the error you're encountering, it's difficult to provide a precise solution. However, here are a few general troubleshooting steps you can take based on the knowledge sources provided: 1. Check your WSL setup: Ensure you're running your commands through WSL if you're on Windows. This is a common issue that can cause commands to fail (source (https://discord.com/channels/686873244791210014/1212373984453075004)). 2. Check for compilation errors: If there's a problem with your Wasp code, wasp start might fail. Look for any error messages in your terminal that might indicate a problem with your code (source (https://discord.com/channels/686873244791210014/1218333969720938506)). 3. Check your project's dependencies: If there's a problem with the dependencies in your project, wasp start might fail. For example, you might see an EACCES error if there's a permissions issue with your node_modules directory (source (https://discord.com/channels/686873244791210014/1218333969720938506)). 4. Check your database connection: If your app relies on a database and there's a problem with the database connection, wasp start might fail. For example, you might see an error message about being unable to connect to the database (source (https://discord.com/channels/686873244791210014/1215223623271321661)). If none of these steps help, please provide more information about the error you're encountering so we can better assist you. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @Anddy, 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?

miho•2mo ago

It's better to paste the text into questions so Kapa can read it. wasp db migrate-dev did you run this?

AnddyOP•2mo ago

i have not tried that yet

miho•2mo ago

Are you following the docs? https://docs.opensaas.sh/start/getting-started/

OpenSaaS.sh

Getting Started

Open SaaS is a free, open-source, full-stack SaaS starter kit for React + NodeJS.

AnddyOP•2mo ago

ive been working on this project work weeks now with no errors like this i just tried that and the same issue even did a wasp clean no joy

miho•2mo ago

ive been working on this project work weeks now with no errors like this

What changed today? Did you add some code? Did you delete some code? Did you delete node_modules or .wasp folders?

AnddyOP•2mo ago

i was adding items to main.wasp and creating different queries.. i only deleted those folders via wasp clean

miho•2mo ago

Did you create any crud declarations? Did you run npx prisma commands?

AnddyOP•2mo ago

i did

crud Awards{
  entity: Award,
  operations: {
    create: {
      overrideFn: import { createAward } from "@src/awards/operations"
    }
  }
}

crud Awards{
  entity: Award,
  operations: {
    create: {
      overrideFn: import { createAward } from "@src/awards/operations"
    }
  }
}

miho•2mo ago

Try deleting the crud declarations and let's see what happens to the errors - if they are gone, we can debug further.

AnddyOP•2mo ago

yeah i tried same issue.. its failing while building the SDK @kapa.ai

auth/providers/types.ts(11,37): error TS2694: Namespace '"/root/rackforge/app/.wasp/out/sdk/wasp/node_modules/.prisma/client/index".Prisma' has no exported member 'UserCreateInput'.

why could i get this error?

kapa.ai•2mo ago

Let me check the knowledge base for you. One moment! :books: ---------------------- The error message you're seeing suggests that the UserCreateInput type is not being exported from the Prisma client. This could be due to a few reasons: 1. Prisma client not generated: If the Prisma client has not been generated, or if it was not generated correctly, the UserCreateInput type might not exist. You can try regenerating the Prisma client by running npx prisma generate in your project's root directory. 2. Changes in Prisma version: If you recently upgraded the version of Prisma in your project, it's possible that the UserCreateInput type has been renamed or removed. You can check the Prisma documentation (https://www.prisma.io/docs/) or the Prisma release notes (https://github.com/prisma/prisma/releases) to see if there have been any breaking changes in the version you're using. 3. Changes in your Prisma schema: If you recently made changes to your Prisma schema, it's possible that the UserCreateInput type no longer exists because the corresponding model no longer exists. You can check your schema.prisma file to see if the User model is still there. If none of these suggestions help, please provide more information about your project setup and the changes you've made recently so we can better assist you. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @Anddy, 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?

miho•2mo ago

Could you share your app's code via a Github repo or in a zip file?

AnddyOP•2mo ago

bc20fsM.rar

AnddyOP•2mo ago

sent dm @kapa.ai my prisma generate is going to @prisma not .prisma

kapa.ai•2mo ago

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

miho•2mo ago

I can see you installed a different Prisma version then what Wasp ships with

AnddyOP•2mo ago

yeah i did for an experimental feature

kapa.ai•2mo ago

---------------------- The prisma generate command should generate the Prisma client in the .prisma/client directory of your node_modules folder. If it's generating in the @prisma directory instead, it might be due to a misconfiguration in your Prisma schema file. In your schema.prisma file, you should have a generator block that looks like this:

generator client {
  provider = "prisma-client-js"
  output   = "../node_modules/.prisma/client"
}

generator client {
  provider = "prisma-client-js"
  output   = "../node_modules/.prisma/client"
}

The output field specifies where the Prisma client should be generated. If it's set to @prisma/client or something similar, that could be why your Prisma client is being generated in the wrong location. If your generator block is configured correctly and you're still experiencing this issue, it might be a bug with Prisma. In that case, you should open an issue (https://github.com/prisma/prisma/issues) on the Prisma GitHub repository. For more information, you can refer to the Prisma documentation on generating the Prisma client (https://www.prisma.io/docs/concepts/components/prisma-client/working-with-prismaclient/generating-prisma-client). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @Anddy, 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?

AnddyOP•2mo ago

it was working fine yesterday

miho•2mo ago

I'm telling you the root cause of your problem 🙂 and it couldn't have worked with this Prisma version. I guess you ran npm install prisma at some point. Put "prisma": "4.16.2" in your package.json instead of the version you have now. Also, you can't use relationJoins preview feature since it's a Prisma v5 feature. Prisma v5 will come to Wasp soon, sometime in October.

AnddyOP•2mo ago

ill give that a shot

MEE6•2mo ago

Wohooo @Anddy, you just became a Waspeteer level 3!

miho•2mo ago

Also, delete package-lock.json to make sure it installs both prisma and @prisma/client and do wasp clean.

AnddyOP•2mo ago

yeah it was prisma.. so weird that it was working the other day and then it just stopped

miho•2mo ago

Did you run npm install prisma at some point? That would explain the change in package.json.

Gaming

Programming

wasp app wont start