This looks interesting! I’ll be trying it soon.
Spotlight: Sentry for Development
11–20 of 83 posts
Re: Spotlight: Sentry for Development
#12Earlier quoted context omitted.
https://spotlightjs.com/ doesn't work Only http
What error are you seeing? Works over here. Its hosted on Vercel so shouldn’t be too complicated or different than most similar deployments.
Both say 'Unable to connect' for me (Firefox built in page) in the UK. Which I think means the name resolved but no response. (But I'm on mobile so can't say more than that.)
Re: Spotlight: Sentry for Development
#13Earlier quoted context omitted.
What error are you seeing? Works over here. Its hosted on Vercel so shouldn’t be too complicated or different than most similar deployments.
Both say 'Unable to connect' for me (Firefox built in page) in the UK. Which I think means the name resolved but no response. (But I'm on mobile so can't say more than that.)
Are you using NextDNS by chance? Someone reported an issue with it blocking the domain on there, but it was unclear _which_ setting was blocking it. Was also odd given its just a Vercel website and the domain (afaik) was unused prior.
Re: Spotlight: Sentry for Development
#14Earlier quoted context omitted.
What error are you seeing? Works over here. Its hosted on Vercel so shouldn’t be too complicated or different than most similar deployments.
Both say 'Unable to connect' for me (Firefox built in page) in the UK. Which I think means the name resolved but no response. (But I'm on mobile so can't say more than that.)
The domain name is new, and those get blocked by many DNS-based ad-blocks. I use NextDNS and get the same error - spotlightjs.com is blocked (resolves to 0.0.0.0)
NextDNS calls this "Block Newly Registered Domains (NRDs)", and applies to all domains <30 days. ZScaler has something similar for corporate users, so people connecting from work might see a big red warning page.
Re: Spotlight: Sentry for Development
#15Spotlight has a pretty strong brand name for API dev tool - https://stoplight.io/ Could be confusion
Can we stop this? There's only so many names in this world and we're going to find overlap. If you're afraid of confusing two projects that are two completely separate things just because they share the same name, instead of reading what you're using, that's a you issue, not the projects.
Re: Spotlight: Sentry for Development
#16I am not sure if I fully understand the architecture.
Is the sidecar run on the server or in the client?
Re: Spotlight: Sentry for Development
#17Looks interesting, but I'd rather die that npm-install anything on one of my webapps.
[deleted]
Re: Spotlight: Sentry for Development
#18[deleted]
Re: Spotlight: Sentry for Development
#19I am not sure if I fully understand the architecture. Is the sidecar run on the server or in the client?
Its run on your local device - its just a local devserver that allows Sentry's SDKs to pipe data to it. The overlay (the Spotlight UI) then connects to the sidecar via a Server-Sent Events stream (basically a pubsub HTTP stream which operates unidirectional - think websockets but simpler). This is needed due to the distributed nature of services, but our goal is to push this abstraction into dev servers, e.g. Vite.
Added a ticket to track improving the docs here: https://github.com/getsentry/spotlight/issues/242
Re: Spotlight: Sentry for Development
#20I am not sure if I fully understand the architecture. Is the sidecar run on the server or in the client?
Its run on your local device - its just a local devserver that allows Sentry's SDKs to pipe data to it. The overlay (the Spotlight UI) then connects to the sidecar via a Server-Sent Events stream (basically a pubsub HTTP stream which operates unidirectional - think websockets but simpler). This is needed due to the distributed nature of services, but our goal is to push this abstraction into dev servers, e.g. Vite. A…
ok! thank you