You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever you try to swap the preloaded favicon from the skeleton project to your own, it refuses to do so unless you switch the HTML link to a non-existent path, reload, and set it back.
Reproduction
`Need to install the following packages:
create-svelte@6.0.5
Ok to proceed? (y) y
create-svelte version 6.0.5
┌ Welcome to SvelteKit!
│
◇ Where should we create your project?
│ (hit Enter to use current directory)
│
◇ Which Svelte app template?
│ Skeleton project
│
◇ Add type checking with TypeScript?
│ No
│
◇ Select additional options (use arrow keys/space bar)
│ none
│
└ Your project is ready!
Browsers cache favicon.ico files very aggressively. That's just how they work, it's unrelated to Svelte, and there's not really anything we can reasonably do about that.
Describe the bug
Whenever you try to swap the preloaded favicon from the skeleton project to your own, it refuses to do so unless you switch the HTML link to a non-existent path, reload, and set it back.
Reproduction
`Need to install the following packages:
create-svelte@6.0.5
Ok to proceed? (y) y
create-svelte version 6.0.5
┌ Welcome to SvelteKit!
│
◇ Where should we create your project?
│ (hit Enter to use current directory)
│
◇ Which Svelte app template?
│ Skeleton project
│
◇ Add type checking with TypeScript?
│ No
│
◇ Select additional options (use arrow keys/space bar)
│ none
│
└ Your project is ready!
Install community-maintained integrations:
https://github.com/svelte-add/svelte-add
Next steps:
1: npm install
2: git init && git add -A && git commit -m "Initial commit" (optional)
3: npm run dev -- --open
To close the dev server, hit Ctrl-C
Stuck? Visit us at https://svelte.dev/chat`
Logs
No response
System Info
Severity
serious, but I can work around it
Additional Information
Frustrating since I spent a decent amount of time trying to work with this problem not knowing of its existence.
The text was updated successfully, but these errors were encountered: