Some crazy WASP error!
Hey guys!
This is a different project from my main design one so its pretty new, so i can afford any breaking fixes lol.
I don't know what the heck happened but i get this error:
things are WILDING out.
I think this line is key
Pretty sure it shouldn't be looking there.
Something kind of similar to this happened way back when I was using direct imports but from what I see and done all my imports are relative.
Heres a link to the full WASP project code: https://www.mediafire.com/file/78efctqk6a6e75h/RecruitAI.zip/file
MediaFire
RecruitAI
12 Replies
Hi @Jacob Ferrari. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Sorry @Jacob Ferrari, 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?
Mediafire brings back memoris š let me take a look
Usually, you can start with sharing the Wasp file content in three backticks
on each side, and it will look like this:
```wasp
app RecruitAI {
wasp: {
version: "^0.13.2"
},
title: "RecruitAI",
...
}
route LoginRoute { path: "/login", to: LoginPage }
page LoginPage {
component: import { Login } from "@src/pages/auth.tsx"
}
...
action processWithGPT4 {
fn: import { processWithGPT4 } from "@src/actions.js"
}
query getUser {
fn: import { getUser } from "@src/queries.js",
entities: [User]
}
query getApplicants {
fn: import { getApplicants } from "@src/queries.js",
entities: [Applicant]
}
query getApplicant {
fn: import { getApplicant } from "@src/queries.js",
entities: [Applicant]
}
query getJob {
fn: import { getJob } from "@src/queries.js",
entities: [Job]
}
query getJobs {
fn: import { getJobs } from "@src/queries.js",
entities: [Job]
}
...
api webhookCallback {
fn: import { webhookCallback } from "@src/apis",
middlewareConfigFn: import { webhookCallbackMiddlewareFn } from "@src/apis",
httpRoute: (POST, "/webhook/callback"),
auth: false
}
```
Start with running wasp clean and then again wasp start š while I debug
Could you try removing the .js from the @src/queries.js and just write @src/queries?
And also change @src/actions.js to @src/actions`haha ya fair probably better than just dropping it in mediafire.
wasp clean doesnt fix it.
and sure ! @miho
It works after those changes for me š it seems that might have a bug at our hands @Filip
works!! @miho thank you!!
Weird though! In my other other project it didn't matter if i put .js or .ts
But i had it better organized and it was @src/server/actions.ts in my other project.
Did this maybe cause it? seems unrelated.
In my package.json:
I get:
I had RecruitAI uppercased, i just changed it to: recruitai and it got rid of that warning.
And then LAST thing.
When i do wasp clean, wasp start.
I get:
[ Db ] import { PrismaClient } from '@prisma/client'
[ Db ] const prisma = new PrismaClient()
[ Db ]
---
I can fix that with but i feel like thats weird to have to do after a wasp clean.
Wohooo @Jacob Ferrari, you just became a Waspeteer level 5!
Nice, thank you for the extra feedback! The Prisma erorr is more of a warning because it creates the DB file automatically so it looks worse than it is, really š
okay gotchu! @miho
After i do wasp db migrate-dev it says: And then all errors go away if i then save a file and it recompiles. Is that all good?
After i do wasp db migrate-dev it says: And then all errors go away if i then save a file and it recompiles. Is that all good?
Sounds about right š the project looks interesting, what's the idea behind it?
Okay perfect!
My main company needs to hire dev talent but theres a looot of initital screening involved. So i thought ill just make an AI screener for me.
What it does is take a form submission, then screens them with an LLM, then if they are solid they'll talk to a conversational AI (made with vapi.ai) as an inital interview, then we have an LLM really screen that hard, and if they are over a certain score they can book a interview with my partner and I!
Im making it in WASP because i'd like to allow other people to use this AI Recruitment process eventually!
Awesome! And thanks Jacob for reporting this, it is an actual bug we will be fixing!
No problem! glad to help and thanks again!