Skip to content

docs(faq): add help to debug config issues #1167

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

Merged
merged 3 commits into from
Jul 10, 2025
Merged

docs(faq): add help to debug config issues #1167

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1ea5086
docs(faq): add help to debug config issues
maxlath Jul 10, 2025
4f4c052
use inlined DEBUG env variable
maxlath Jul 10, 2025
c876870
fixup! docs(faq): add help to debug config issues
maxlath Jul 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,13 @@
# Frequently Asked Questions

### Something is wrong with my config, how can I find where the problem comes from?

`vite` and `vite-plugin-svelte` can be made more verbose by using the debug mode (powered by and following the conventions of the [`debug`](https://github.com/debug-js/debug) library):

- `DEBUG=vite-plugin-svelte:config vite dev`: log `vite-plugin-svelte` debug info related to the config
- `DEBUG=vite-plugin-svelte:* vite dev`: log all `vite-plugin-svelte` debug info
- `DEBUG=* vite dev`: log all debug info

### Why is component state reset on HMR update?

Preservation of local component state after JS updates is disabled to avoid unpredictable and error-prone behavior.
Expand Down