Cannot find package 'vitest' imported from
Fresh installment of wasp 0.15.2 with opensaas gives me this - i already tried doing
wasp clean
3 Replies
Hi @InsOp. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the information provided in the knowledge sources, it seems that you're encountering an issue with the Vitest package, which is used for testing in Wasp projects. While the exact error message you're seeing isn't directly addressed in the provided documents, I can offer some insights and suggestions based on related information.
First, it's good that you've already tried
wasp clean, as this is often a helpful step in resolving various issues. As mentioned in the CLI Reference, wasp clean removes all generated code and cached artifacts, which can sometimes solve dependency-related problems.
However, since the issue persists, here are a few additional steps you could try:
1. Ensure that you've run wasp start after cleaning the project. This command compiles your Wasp project and should install the necessary dependencies, including Vitest.
2. If the problem continues, you might want to try running wasp db migrate-dev as suggested in one of the Discord support threads. This step can sometimes help resolve dependency issues.
3. Check if there are any network-related issues that might be preventing the installation of packages. As mentioned in one of the Discord threads, slow or unstable networks can sometimes cause npm installation problems.
4. Make sure you're not running wasp test while wasp start is active, as mentioned in the Testing Your React App documentation.
If none of these steps resolve the issue, it might be worth checking if there's a problem with the specific version of the OpenSaaS template you're using with Wasp 0.15.2. Unfortunately, the provided knowledge sources don't contain enough information to determine if there's a known compatibility issue between these specific versions.
If the problem persists, you may want to reach out to the Wasp community on their Discord channel for more specific assistance, as they might have encountered similar issues with the latest versions.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @InsOp, 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?when installing it manually inside
app/.wasp/out/web-app he then tells me that he didnt find autoprefixer axios as well
looks like the problem is a faulty npm install which is reprroducable 95% of the time
but more like a me-problem
this framework is really wack. got it to work, created a schema change, made the migraion. and now packages are missing again?
first nodemon, then dotenvthis framework is really wackLet's unwack it together then 🙂 Could you walk me through what you did and what happened? I guess,
wasp new app -t saas and then wasp start or something like that? Did you wait for npm install to finish or maybe you interruputed it?