8000 SvelteKit (Vite) hot reload requires reloading the extension (Firefox) · Issue #189 · sveltejs/svelte-devtools · GitHub
[go: up one dir, main page]
Skip to content

SvelteKit (Vite) hot reload requires reloading the extension (Firefox) #189

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
davidjayb opened this issue Mar 29, 2024 · 3 comments
Closed

SvelteKit (Vite) hot reload requires reloading the extension (Firefox) #189

davidjayb opened this issue Mar 29, 2024 · 3 comments
Labels
duplicate This issue or pull request already exists

Comments

@davidjayb
Copy link
Contributor

Describe the bug
Using SvelteKit with Vite, every time there is a code update served by Vite the Svelte Devtools needs to be reloaded. The plugin becomes unresponsive until reloaded.

To Reproduce
Steps to reproduce the behavior:

  1. Open Svelte Devtools
  2. Go to your webpage
  3. Update a page/component

Expected behavior
When a component is updated the plugin should reflect the updated code without requiring closing the devtools and re-opening.

Environment

  • Firefox 124.0.1
  • built from master
  • Svelte 4.2.11

Additional context

This seems to be a Firefox specific bug, or related to changes in master that have not been released. Using Chrome with the extension from the marketplace I was unable to reproduce this bug.
@ignatiusmb
Copy link
Member

Would it be possible for you to record the behavior? I couldn't seem to make it unresponsive with a fresh Svelte+Vite or SvelteKit project, the only issue I can see is with HMR which is reported in #125

@ignatiusmb ignatiusmb added the pending The issue still hasn't been fully clarified label Apr 1, 2024
@davidjayb
Copy link
Contributor Author

Ah yes, it is related to HMR.

@ignatiusmb
Copy link
Member

Thanks for the confirmation, closing in favor of #125

@ignatiusmb ignatiusmb closed this as not planned Won't fix, can't repro, duplicate, stale Apr 2, 2024
@ignatiusmb ignatiusmb added duplicate This issue or pull request already exists and removed pending The issue still hasn't been fully clarified labels Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate This issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ignatiusmb @davidjayb
0