Closed Guilherme-Vasconcelos closed 8 months ago
It seems like I figured out the issue: because I used npm create tauri-app@latest .
(to initialize the project in the current directory, which should be allowed according to create-tauri-app's README), my package.productName
in src-tauri/tauri.conf.json
was set to "."
. I changed it to "my-tauri-app"
and now it works.
Why is this issue closed if nothing was done to address the problem? Users expect running create-tauri-app
with the current directory passed should either set the app name to the current directory or prompt for an app name
Describe the bug
I have just created a brand new tauri project using create-tauri-app. Then I ran
npm install
, followed bynpm run tauri dev
and got this panic:Despite the panic, I can open
http://localhost:1420/
in my browser and it displays the default tauri page, so I'm not really sure what effect the panic had but it doesn't seem to have affected the startup:Reproduction
Run the following commands:
mkdir my-tauri-app
cd my-tauri-app
npm create tauri-app@latest . --template svelte-ts --manager npm
In the create-tauri-app interface, pick the following:
Wait for the project to be generated, then run the following commands:
npm install
npm run tauri dev
You should see the panic I mentioned in the description field.
Expected behavior
I expected the default generated project to run without panics.
Full
tauri info
output