Wasp•2y ago

type declarations

Cannot find module 'wasp/client/router' or its corresponding type declarations.ts(2307)

how do i download the type declarations

kapa.ai•7/7/24, 12:30 PM

Hi @ArDev. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

kapa.ai•7/7/24, 12:30 PM

----------------------
The error message you're seeing typically occurs when the Wasp compiler hasn't been run or something has gone wrong during the compilation process. The Wasp compiler generates the necessary wasp/*wasp/* packages, including wasp/client/routerwasp/client/router, which includes the type declarations you need.

Here are a few steps you can try to resolve this issue:

Check your Wasp version with wasp versionwasp version. Make sure it's up to date.
Try running the Wasp compiler with wasp startwasp start. This should generate the necessary wasp/*wasp/* packages.
If the error persists, you might need to clean your Wasp project. You can do this by running wasp cleanwasp clean. This command deletes all .wasp.wasp and
```
node_modules
```
```
node_modules
```
files. After running wasp cleanwasp clean, try running wasp startwasp start again to reinstall everything.

If none of these steps resolve your issue, it might be helpful to provide more information about your project setup or any specific steps you took before encountering this error.

Sources:

Discord support thread: Hey! Any ideas on some solutions to these errors? > Answers (🙋questionsHey! Any ideas on some solutions to these errors?)
Docs > Advanced > Type-Safe Links > API Reference > routesroutes Object (https://wasp-lang.dev/docs/advanced/links#routes-object)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•7/7/24, 12:30 PM

Sorry @ArDev, 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•7/7/24, 12:51 PM

Can you share some details about your setup: your OS, how did you create your project and what commands did you run?

ArDevOP•7/9/24, 5:59 PM

@kapa.ai Cannot find module 'wasp/entities' or its corresponding type declarations.ts(23)

this is in opensaas

kapa.ai•7/9/24, 5:59 PM

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

kapa.ai•7/9/24, 5:59 PM

----------------------
The error message you're seeing typically occurs when the Wasp compiler hasn't been run or something has gone wrong during the compilation process. The Wasp compiler generates the necessary wasp/*wasp/* packages, including wasp/entitieswasp/entities, which includes the type declarations you need.

Here are a few steps you can try to resolve this issue:

Check your Wasp version with wasp versionwasp version. Make sure it's up to date.
Try running the Wasp compiler with wasp startwasp start. This should generate the necessary wasp/*wasp/* packages.
If the error persists, you might need to clean your Wasp project. You can do this by running wasp cleanwasp clean. This command deletes all .wasp.wasp and
```
node_modules
```
```
node_modules
```
files. After running wasp cleanwasp clean, try running wasp startwasp start again to reinstall everything.

If none of these steps resolve your issue, it might be helpful to provide more information about your project setup or any specific steps you took before encountering this error.

Sources:

Discord support thread: Hey! Any ideas on some solutions to these errors? > Answers (🙋questionsHey! Any ideas on some solutions to these errors?)
Docs > Advanced > Type-Safe Links > API Reference > routesroutes Object (https://wasp-lang.dev/docs/advanced/links#routes-object)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

ArDevOP•7/9/24, 6:07 PM

@kapa.ai error: database "OpenSaaS-ceab7ead0a" does not exist
[ Server!] at /mnt/d/AI Projects/aiwrapper1/app/node_modules/pg-pool/index.js:45:11
[ Server!] at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[ Server!] at async Db.executeSql (/mnt/d/AI Projects/aiwrapper1/app/node_modules/pg-boss/src/db.js:28:14)
[ Server!] at async Contractor.isInstalled (/mnt/d/AI Projects/aiwrapper1/app/node_modules/pg-boss/src/contractor.js:32:20)
[ Server!] at async Contractor.start (/mnt/d/AI Projects/aiwrapper1/app/node_modules/pg-boss/src/contractor.js:37:23)
[ Server!] at async PgBoss.start (/mnt/d/AI Projects/aiwrapper1/app/node_modules/pg-boss/src/index.js:103:5)
[ Server!] at startPgBoss (/mnt/d/AI Projects/aiwrapper1/app/.wasp/out/sdk/wasp/server/jobs/core/pgBoss/pgBoss.ts:63:5)
[ Server!] at startServer (/mnt/d/AI Projects/aiwrapper1/app/.wasp/out/server/src/server.ts:14:3) {
[ Server!] length: 105,
[ Server!] severity: 'FATAL',
[ Server!] code: '3D000',
[ Server!] detail: undefined,
[ Server!] hint: undefined,
[ Server!] position: undefined,
[ Server!] internalPosition: undefined,
[ Server!] internalQuery: undefined,
[ Server!] where: undefined,
[ Server!] schema: undefined,
[ Server!] table: undefined,
[ Server!] column: undefined,
[ Server!] dataType: undefined,
[ Server!] constraint: undefined,
[ Server!] file: 'postinit.c',
[ Server!] line: '1019',
[ Server!] routine: 'InitPostgres'
[ Server!] }
[ Server ] Server listening on port 3001
[ Server!] node:internal/process/promises:288
[ Server!] triggerUncaughtException(err, true /* fromPromise */);
[ Server!] ^
[ Server!]
[ Server!] [UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "#<PgBoss>".] {
[ Server!] code: 'ERR_UNHANDLED_REJECTION'
[ Server!] }
[ Server!]
[ Server!] Node.js v18.20.3
[ Server ] [nodemon] app crashed - waiting for file changes before starting...

kapa.ai•7/9/24, 6:07 PM

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

kapa.ai•7/9/24, 6:08 PM

----------------------
The error message you're seeing suggests that the PostgreSQL database "OpenSaaS-ceab7ead0a" does not exist. This could be due to a few reasons:

The database was not created: Ensure that you have run the necessary commands to create the database. In the context of Wasp, this is usually done with the wasp db migrate-devwasp db migrate-dev command.
The database name is incorrect: Double-check the database name in your Wasp project configuration. Make sure it matches the name of the database you've created.
Connection issues: There might be issues with how your application is trying to connect to the database. Ensure that the database is running and that the connection parameters (host, port, username, password) are correct.

As for the UnhandledPromiseRejectionUnhandledPromiseRejection error, it's generally a good practice to always handle promises with a .catch().catch() block to handle any errors that might occur. This can help prevent unhandled promise rejections which can lead to application crashes.

Unfortunately, without more information about your project setup or the specific steps you took before encountering this error, it's hard to provide a more specific solution. If none of the above suggestions help, please provide more details about your issue.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•7/9/24, 6:08 PM

Sorry @ArDev, 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?

ArDevOP•7/9/24, 7:34 PM

@kapa.ai how can i manually install the dependencies?

kapa.ai•7/9/24, 7:34 PM

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

MEE6•7/9/24, 7:34 PM

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

kapa.ai•7/9/24, 7:34 PM

----------------------
To manually install the dependencies in a Wasp project, you need to navigate to the appropriate directories and run

npm install

npm install

. Here are the steps:

Run the wasp compilewasp compile command. This is an internal command that won't start the project but will generate the necessary files.
Navigate to the .wasp/out/web-app.wasp/out/web-app directory and run
```
npm install
```
```
npm install
```
there.

cd .wasp/out/web-app
npm install

cd .wasp/out/web-app
npm install

Navigate to the .wasp/out/server.wasp/out/server directory and run
```
npm install
```
```
npm install
```
there.

cd ../server
npm install

cd ../server
npm install

These steps simulate what Wasp usually does on its own. By running them manually, you might see more detailed error messages if something goes wrong.

Source: Discord support thread: OpenSaas setup 'Role postgres does not exist' > Answers Part 2 (🙋questionsOpenSaas setup 'Role postgres does not exist')
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•7/9/24, 7:34 PM

Sorry @ArDev, 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?

ArDevOP•7/9/24, 7:34 PM

im talking about the type declarations @kapa.ai

kapa.ai•7/9/24, 7:34 PM

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

kapa.ai•7/9/24, 7:34 PM

----------------------
The type declarations in Wasp are automatically generated when you run the Wasp compiler with wasp startwasp start. These type declarations are part of the wasp/*wasp/* packages that the compiler generates, and they are based on the declarations in your Wasp files.

If you're seeing errors related to these type declarations, it's likely that the Wasp compiler hasn't been run or something has gone wrong during the compilation process.

Unfortunately, there isn't a way to manually install these type declarations. They are an integral part of the Wasp compiler's output and are tightly coupled to your Wasp project's specific configuration and code.

If you're having trouble with these type declarations, I would recommend trying the following steps:

Run wasp startwasp start to start the Wasp compiler. This should generate the necessary wasp/*wasp/* packages, including the type declarations.
If the error persists, try cleaning your Wasp project with wasp cleanwasp clean. This command deletes all .wasp.wasp and
```
node_modules
```
```
node_modules
```
files. After running wasp cleanwasp clean, try running wasp startwasp start again.

If none of these steps resolve your issue, it might be helpful to provide more information about your project setup or any specific steps you took before encountering this error.

Sources:

Discord support thread: Hey! Any ideas on some solutions to these errors? > Answers (🙋questionsHey! Any ideas on some solutions to these errors?)
Docs > Advanced > Type-Safe Links > API Reference > routesroutes Object (https://wasp-lang.dev/docs/advanced/links#routes-object)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•7/9/24, 7:35 PM

Sorry @ArDev, 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?

ArDevOP•7/9/24, 7:43 PM

2024-07-09 18:07:21.369 UTC [34] FATAL: database "OpenSaaS-ceab7ead0a" does not exist @kapa.ai

kapa.ai•7/9/24, 7:43 PM

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

kapa.ai•7/9/24, 7:43 PM

----------------------
The error message you're seeing suggests that the PostgreSQL database "OpenSaaS-ceab7ead0a" does not exist. This could be due to a few reasons:

The database was not created: Ensure that you have run the necessary commands to create the database. In the context of Wasp, this is usually done with the wasp db migrate-devwasp db migrate-dev command.
The database name is incorrect: Double-check the database name in your Wasp project configuration. Make sure it matches the name of the database you've created.
Connection issues: There might be issues with how your application is trying to connect to the database. Ensure that the database is running and that the connection parameters (host, port, username, password) are correct.

Unfortunately, without more information about your project setup or the specific steps you took before encountering this error, it's hard to provide a more specific solution. If none of the above suggestions help, please provide more details about your issue.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•7/9/24, 7:43 PM

Sorry @ArDev, 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?

Mmiho Can you share some details about your setup: your OS, how did you create your pr...

ArDevOP•7/9/24, 8:54 PM

Windows

ArDevOP•7/9/24, 8:55 PM

using Cursor ide, did every command mentioned in the opensaas docs

ArDevOP•7/9/24, 8:55 PM

for installation

ArDevOP•7/10/24, 5:51 PM

@kapa.ai what cna i do?

kapa.ai•7/10/24, 5:51 PM

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

kapa.ai•7/10/24, 5:51 PM

----------------------
Based on the error message you're seeing, it seems like the PostgreSQL database "OpenSaaS-ceab7ead0a" does not exist. Here are some steps you can take to resolve this issue:

Create the database: In the context of Wasp, you can usually do this with the wasp db migrate-devwasp db migrate-dev command. This command creates the database and applies any pending migrations.
Check the database name: Make sure the database name in your Wasp project configuration matches the name of the database you've created.
Check your database connection: Ensure that the database is running and that the connection parameters (host, port, username, password) are correct.
Check Docker permissions: If you're using Docker, make sure it's set up properly. You might need to follow this guide: Manage Docker as a non-root user (https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user)
Clean and restart your Wasp project: If none of the above steps work, you can try cleaning your Wasp project with wasp cleanwasp clean. This command deletes all .wasp.wasp and
```
node_modules
```
```
node_modules
```
files. After running wasp cleanwasp clean, try running wasp startwasp start again.

If none of these steps resolve your issue, it might be helpful to provide more information about your project setup or any specific steps you took before encountering this error.

Sources:

Discord support thread: Cant start database docker is not working on wsl properly > Answers Part 6 (🙋questionsCant start database docker is not working on wsl properly)
Discord support thread: [SOLVED] OpenSaaS installation docker and db issue > Answers (🙋questions[SOLVED] OpenSaaS installation docker and db issue)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•7/10/24, 5:51 PM

Sorry @ArDev, 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?

ArDevOP•7/10/24, 8:05 PM

@kapa.ai how do i fix this issue import { cn } from '../../shared/utils';

kapa.ai•7/10/24, 8:05 PM

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

kapa.ai•7/10/24, 8:05 PM

----------------------
The error you're seeing might be due to incorrect import paths. In Wasp, the @shared@shared alias is used to import shared code between the server and the client. However, it seems like this alias was not converted correctly in some cases, as mentioned in this Discord support thread (🙋questionsMissing "./auth/email" specifier in "wasp" package).

To fix this issue, you should replace ../../shared/utils../../shared/utils with @shared/utils@shared/utils in your import statement:

import { cn } from '@shared/utils';

import { cn } from '@shared/utils';

If this doesn't resolve your issue, please provide more information about your project setup or the specific steps you took before encountering this error.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•7/10/24, 8:05 PM

Sorry @ArDev, 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?

ArDevOP•7/10/24, 8:05 PM

@kapa.ai how do i fix this issue - Cannot find module 'wasp/client/router' or its corresponding type declarations.ts(2307)

kapa.ai•7/10/24, 8:05 PM

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

kapa.ai•7/10/24, 8:05 PM

Check your Wasp version with wasp versionwasp version. Make sure it's up to date.
Try running the Wasp compiler with wasp startwasp start. This should generate the necessary wasp/*wasp/* packages.
If the error persists, you might need to clean your Wasp project. You can do this by running wasp cleanwasp clean. This command deletes all .wasp.wasp and
```
node_modules
```
```
node_modules
```
files. After running wasp cleanwasp clean, try running wasp startwasp start again to reinstall everything.

If none of these steps resolve your issue, it might be helpful to provide more information about your project setup or any specific steps you took before encountering this error.

Sources:

Discord support thread: Hey! Any ideas on some solutions to these errors? > Answers (🙋questionsHey! Any ideas on some solutions to these errors?)
Docs > Advanced > Type-Safe Links > API Reference > routesroutes Object (https://wasp-lang.dev/docs/advanced/links#routes-object)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•7/10/24, 8:05 PM

Sorry @ArDev, 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?

ArDevOP•7/10/24, 8:13 PM

it still cannot see the wasp types @kapa.ai

kapa.ai•7/10/24, 8:13 PM

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

kapa.ai•7/10/24, 8:13 PM

----------------------
If you're still having trouble with Wasp not being able to find the type declarations, it might be due to a more complex issue. Here are a few additional steps you can try:

Check your project structure: Make sure your Wasp project structure is correct and that all necessary files are in the right place. The Wasp compiler relies on a specific project structure to generate the wasp/*wasp/* packages.
Check your Wasp code: Errors in your Wasp code could prevent the compiler from generating the wasp/*wasp/* packages correctly. Make sure all your Wasp code is correct and try running the compiler again.
Reinstall Wasp: If none of the above steps work, you might need to reinstall Wasp. You can do this by first uninstalling Wasp with npm uninstall -g waspnpm uninstall -g wasp, and then reinstalling it with npm install -g waspnpm install -g wasp.
Reach out to the Wasp community: If you're still having trouble, you might want to reach out to the Wasp community for help. You can do this through the Wasp Discord server (🙋questionsHey! Any ideas on some solutions to these errors?) or by opening an issue on the Wasp GitHub repository (https://github.com/wasp-lang/wasp).

Remember, the type declarations are an integral part of the Wasp compiler's output and are tightly coupled to your Wasp project's specific configuration and code. If you're having trouble with these type declarations, it's likely that there's an issue with your project setup or the Wasp compiler itself.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•7/10/24, 8:13 PM

Sorry @ArDev, 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?

ArDevOP•7/10/24, 8:15 PM

could it do with my bashrc file @kapa.ai

kapa.ai•7/10/24, 8:15 PM

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

kapa.ai•7/10/24, 8:15 PM

----------------------
The .bashrc.bashrc file is used to configure your shell session, including setting environment variables and defining shell functions. It's unlikely that this file would directly affect the generation of type declarations in a Wasp project.

However, if your PATHPATH environment variable isn't correctly configured in your .bashrc.bashrc file, it could potentially cause issues with running the Wasp compiler. The PATHPATH environment variable is used by your shell to determine where to look for executable files, so if Wasp isn't installed in a directory listed in your PATHPATH, your shell won't be able to find and run the Wasp compiler.

You can check if this is the issue by running echo $PATHecho $PATH in your shell. This will print out the directories listed in your PATHPATH environment variable. If the directory where Wasp is installed isn't listed, you'll need to add it.

Here's how you can add a directory to your PATHPATH in your .bashrc.bashrc file:

Open your .bashrc.bashrc file in a text editor.
Add the following line at the end of the file, replacing /path/to/wasp/path/to/wasp with the actual directory where Wasp is installed:

export PATH=$PATH:/path/to/wasp

export PATH=$PATH:/path/to/wasp

Save the changes and close the file.
Reload your .bashrc.bashrc file by running source ~/.bashrcsource ~/.bashrc in your shell.

After doing this, try running the Wasp compiler again with wasp startwasp start to see if the issue is resolved.

Sources:

Discord support thread: Getting started with Wasp on Terminal > Answers (🙋questionsGetting started with Wasp on Terminal)
Github Issue (closed): Update wasp completionwasp completion help to mention .zshrc.zshrc for MacOS > Original post (https://github.com/wasp-lang/wasp/issues/948)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•7/10/24, 8:15 PM

Sorry @ArDev, 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?

ArDevOP•7/10/24, 8:24 PM

@kapa.ai how to install the types in a new opensaas project

kapa.ai•7/10/24, 8:24 PM

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

kapa.ai•7/10/24, 8:24 PM

----------------------
When you create a new OpenSaaS project with Wasp, the necessary type declarations should be automatically generated when you run the Wasp compiler with wasp startwasp start. These type declarations are part of the wasp/*wasp/* packages that the compiler generates, and they are based on the declarations in your Wasp files.

Here are the steps to create a new OpenSaaS project and install the types:

Create a new OpenSaaS project with the following command:

wasp new <project-name> -t saas

wasp new <project-name> -t saas

Replace <project-name><project-name> with the name of your project.

Navigate to your new project directory:

cd <project-name>

cd <project-name>

Start the Wasp compiler:

wasp start

wasp start

This command starts the Wasp development server and also triggers the Wasp compiler, which generates the necessary wasp/*wasp/* packages, including the type declarations.

If you're seeing errors related to these type declarations, it's likely that the Wasp compiler hasn't been run or something has gone wrong during the compilation process. In that case, you might need to clean your Wasp project with wasp cleanwasp clean and then run wasp startwasp start again.

Sources:

Docs > General > CLI Reference > Commands > Creating a New Project (https://wasp-lang.dev/docs/general/cli#creating-a-new-project)
Docs > Project > Starter Templates > Available Templates (https://wasp-lang.dev/docs/project/starter-templates#available-templates)
Discord support thread: Hey! Any ideas on some solutions to these errors? > Answers (🙋questionsHey! Any ideas on some solutions to these errors?)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

type declarations

Similar Threads

Similar Threads

Similar Threads