This doesn't seem to be it, but I always wondered if it would make sense to have an extension to the IDE that uses the aggregated data from Sentry to highlight lines of code that have caused errors or slowdowns.
Spotlight: Sentry for Development
81–83 of 83 posts
Re: Spotlight: Sentry for Development
#82It seems to be getting more and more common to leave your git repository completely undocumented. If you're releasing a software project on github, I want to read about it on github. A basic README that outlines what it does, how it does it, and basic syntax - this is really easy. Table stakes, I might say. I can checkout your repo and I have everything I need to work
It's a terrible habit. Documentation is a nonfunctional requirement. It should describe what is not obvious to someone new and the value of it. Without the conveyance of utility and purpose, all of a project's potential value goes to waste with foot-gunning accuracy.
Re: Spotlight: Sentry for Development
#83Earlier quoted context omitted.
Hey David! Few questions: I'm slightly stuck with the Vite plugin Currently getting this when trying to do an npm run dev: [plugin externalize-deps] No known conditions for "./vite-plugin" entry in "@spotlightjs/sidecar" package The plugin "externalize-deps" was triggered by this import vite.config.ts:7:29: 7 │ import spotlightSidecar from '@spotlightjs/sidecar/vite-plugin'; Should I be telling externalize-deps to le…
Let me circle back on the Vite issue. Bundles are the biggest challenge when doing this turns out :) Would you mind opening a GitHub so we can circle back there? Regarding .NET - it’s coming to all Sentry SDKs (even mobile!). They were looking at .NET already but I’m not sure off hand what prevented its release. I’d expect our other core languages have full support in the next 60 days.
> Let me circle back on the Vite issue. Bundles are the biggest challenge when doing this turns out :)
>
> Would you mind opening a GitHub so we can circle back there?
For anyone else in this boat, I got it working by adding "type": "module" to my package.json file. Getting Tailwind to play nice with this was a bit of a battle, and I didn't manage to figure out how to import the defaultTheme properly, but Spotlight works flawlessly and the Vite plugin auto-starts the sidecar.