PulseDev for SvelteKit.Click it, fix the .svelte.
Click any element in your running SvelteKit app and say what’s wrong. Your agent opens the component behind it, and Vite HMR shows the edit before you approve the diff.
One minute of setup.
None of it ships.
Paste one tag into src/app.html and start your dev server. Keep the PulseDev app open while you work; it runs the server the widget talks to.
- Add
Paste the script tag.
Put it in src/app.html, the layout every page shares. Remove the tag, or keep it out of production builds.
src/app.html <!-- just before </body>, dev only --> <script src="http://localhost:3899/widget.js" data-token="YOUR_TOKEN"></script> - Run
Start SvelteKit as usual.
The widget shows up in the corner of every page. Click it, then click the element you want changed.
terminal $npm run dev➜Local:http://localhost:5173/➜PulseDev:widget connected
It fits how
SvelteKit works.
A click carries more than a selector. The page, the element and its selector go to your agent, which follows them to the right file.
Runes Inspector
View $state, $derived, and $effect runes with their current values inline.
Load Function Debugging
Inspect +page.ts and +layout.ts load function data as it flows into components.
Form Actions
Debug SvelteKit form actions with request/response details and validation state.
Server Route Debugging
Inspect +server.ts endpoints with inline request/response data.
SvelteKit questions.
- Does it work with Svelte 5?
- Yes! PulseDev fully supports Svelte 5 runes and the new reactive system.
- Can I debug load functions?
- Absolutely. PulseDev traces data from load functions directly into your components.
- Does it support scoped styles?
- Yes, PulseDev understands Svelte's scoped CSS and generates fixes that follow your styling patterns.
- Is there a performance overhead?
- PulseDev only runs in development. It is completely stripped from your production builds.
Your SvelteKit app is running.Go point at the bug.
Windows coming soon. Free to start.