Welcome to svelte-trace Discussions! #1
Pinned
Git002
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Welcome Devs 🎉
We’re using Discussions as a place to connect with other members of our community. We hope that you:
build together 💪
The Problem We're Solving Right Now
How many times have you been debugging/exploring a Svelte app, and thought: "Where the heck is this component defined?" You end up playing hide-and-seek with your file tree, searching through folders, or using "Find in Files" just to locate a simple component.
The Solution
With
svelte-trace
, that friction is gone. Just Ctrl + Click (or Cmd + Click) any element in your browser during development, and it instantly opens the exact file and line in VS Code. No more hunting, no more guessing—just instant navigation from your rendered app back to your source code.What's Next
This is where your input becomes invaluable! I'm thinking about:
I Need Your Help
Since this is a BETA release, I'm actively looking for:
💭 Discussion Topics
I'd love to hear your thoughts on:
🙏 Final Thoughts
This project started from my own frustration with component hunting, and I believe it can make all our lives as Svelte developers a bit easier. I need the collective wisdom of this amazing community.
Every bug report, feature request, and piece of feedback helps shape where this goes next.
Ready to give it a spin? Drop your experiences, questions, or wild ideas below! Let's build something awesome together. 🚀
Happy coding, and thanks for reading ✨
Beta Was this translation helpful? Give feedback.
All reactions