Spotlight: Sentry for Development • Hacker News Board

Re: Spotlight: Sentry for Development

#71

Post by ren_engineer » Wed, Dec 06, 2023, 11:47 PM UTC

kunwon1 wrote: post #59

It 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

a lot of "open source" companies leave their repos bare so you are forced to go onto their website where they can better track and retarget you

Re: Spotlight: Sentry for Development

#72

Post by brungarc » Thu, Dec 07, 2023, 12:03 AM UTC

lol768 wrote: post #64

zeeg wrote: post #2

David from Sentry here. If yall have feedback around Spotlight we’d love to hear it. This is a passion project for a few of us and seemed like a natural fit for our technology, and becomes especially interesting with the service oriented world we all find ourselves in.

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…

Thanks for asking, created a ticket for .NET support here: https://github.com/getsentry/sentry-dotnet/issues/2955

I'm actually looking forward to it, I wanted to try on NuGet Trends but stopped on the first hurdle: https://github.com/dotnet/nuget-trends/pull/247

Re: Spotlight: Sentry for Development

#73

Post by joshmanders » Thu, Dec 07, 2023, 2:34 AM UTC

ren_engineer wrote: post #71

kunwon1 wrote: post #59

It 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

a lot of "open source" companies leave their repos bare so you are forced to go onto their website where they can better track and retarget you

Retarget you for what? "Hey you should come back and read the docs on our open source project you were interested in last week"

Re: Spotlight: Sentry for Development

#74

Post by bentlegen » Thu, Dec 07, 2023, 2:40 AM UTC

ren_engineer wrote: post #71

kunwon1 wrote: post #59

It 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

a lot of "open source" companies leave their repos bare so you are forced to go onto their website where they can better track and retarget you

I assume you're not talking about this company because there is no such script on spotlightjs.com (easily verifiable), and the docs are also actually in the repository:

Example: https://github.com/getsentry/spotlight/blob/main/packages/we...

Re: Spotlight: Sentry for Development

#75

Post by boxed » Thu, Dec 07, 2023, 2:50 AM UTC

zeeg wrote: post #56

qxxx wrote: post #47

Earlier quoted context omitted.

I also have no idea what it does. "Sentry for development", so it works like sentry but the errors are streamed to localhost??

That’s a good way to think about it yeah. It’s not 1:1, and also can be extended beyond Sentry, but that was our MVP.

I don't understand the use case. If it's local, I'll just get a nice traceback and I can use the normal debugger. So what's the point of this?

Re: Spotlight: Sentry for Development

#76

Post by gapchuboy » Thu, Dec 07, 2023, 2:55 AM UTC

joshmanders wrote: post #73

ren_engineer wrote: post #71

Earlier quoted context omitted.

a lot of "open source" companies leave their repos bare so you are forced to go onto their website where they can better track and retarget you

Retarget you for what? "Hey you should come back and read the docs on our open source project you were interested in last week"

Hey I see you are interested in spotlight and 78 other things and your ip belongs to fortune 1k. May be you should buy the sentry enterprise license. Just my ads. I work on martech.

Re: Spotlight: Sentry for Development

#77

Post by KTibow » Thu, Dec 07, 2023, 3:52 AM UTC

Nthringas wrote: post #65

pb060 wrote: post #27

May I suggest adding some additional context to the home page? While I heard about Sentry I find difficult to understand what Spotlight does. I might not be the intended target audience though.

it looks to me like it covers the same funcionality as browser developer tools but I am also pretty sure those are going away soon, which will mean the only way to inspect websites will be using tools like this (+ WASM binary formats + google controlled web-runtime[0] means the open web is not open anymore) [0] https://thewebshowcase.withgoogle.com/bring-code-from-platfo...

What? JS isn't getting replaced by WASM. Also some quick Googling says WASM is a joint project by the W3C and multiple browser owners, and debug tools exist for it in Chrome and Firefox already

Re: Spotlight: Sentry for Development

#78

Post by zubairq » Thu, Dec 07, 2023, 4:37 AM UTC

Will give it a spin, always looking for better debug tools, thanks!

Re: Spotlight: Sentry for Development

#79

Post by simonbarker87 » Thu, Dec 07, 2023, 6:11 AM UTC

pb060 wrote: post #27

May I suggest adding some additional context to the home page? While I heard about Sentry I find difficult to understand what Spotlight does. I might not be the intended target audience though.

I agree and find this is the case for many projects like this. I read the homepage and have no idea what the tool does and why I might find it helpful, it wasn’t until I read the inset block on the “Getting Started” page for this one that I had even an inkling what it did.

Most of these types of home page seem to be written assuming I already know what their tool does.

Re: Spotlight: Sentry for Development

#80

Post by the_mitsuhiko » Thu, Dec 07, 2023, 7:56 AM UTC

boxed wrote: post #75

zeeg wrote: post #56

Earlier quoted context omitted.

That’s a good way to think about it yeah. It’s not 1:1, and also can be extended beyond Sentry, but that was our MVP.

I don't understand the use case. If it's local, I'll just get a nice traceback and I can use the normal debugger. So what's the point of this?

Not in all cases do you get a traceback into the UI. In some cases you have to look at your terminal or console. In this case it goes straight into your browser window. But additionally it also shows you a bunch of traces going on for instrumented calls.