Is it compatible with Sentry API (drop in replacement)?
Spotlight: Sentry for Development
41–50 of 83 posts
Re: Spotlight: Sentry for Development
#42May 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.
Re: Spotlight: Sentry for Development
#43Feature request: documentation for running this with a Python web app. It looks to me like it should work - the Python Sentry library can presumably publish to the local Spotlight forwarder. I don't have a npm/npx/etc build mechanism setup, so I'd appreciate instructions for running a separate web server to serve the UI, rather than running the UI integrated directly into my existing Python web application.
Would a bundled JS asset work for the UI? Eg something from a CDN? Feel free to add a GitHub issue with more details if that’s easier!
Or even something like "npx sentry-spotlight-http-server" which starts a server running containing the UI.
Re: Spotlight: Sentry for Development
#44Earlier quoted context omitted.
I'm curious. I figure you considered building the UI as a DevTools extension; why 'd you go this in-page-DOM-overlay route instead?
More control and far lower barrier to hack on. This actually opens up a lot of doors for us even if you ignore usability and discoverability. For example, we have a POC that pops the overlay when a server error happens, giving you a rich debug experience where otherwise you might not be able to have one.
Re: Spotlight: Sentry for Development
#45Earlier quoted context omitted.
Would a bundled JS asset work for the UI? Eg something from a CDN? Feel free to add a GitHub issue with more details if that’s easier!
Yeah, a CDN link would be fine - anything that means I don't have to figure out how to run "npm install" for a project which isn't using that yet. Or even something like "npx sentry-spotlight-http-server" which starts a server running containing the UI.
npx @spotlightjs/spotlightRe: Spotlight: Sentry for Development
#46David 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.
Re: Spotlight: Sentry for Development
#47May 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.
Re: Spotlight: Sentry for Development
#48Earlier quoted context omitted.
Yeah, a CDN link would be fine - anything that means I don't have to figure out how to run "npm install" for a project which isn't using that yet. Or even something like "npx sentry-spotlight-http-server" which starts a server running containing the UI.
Maybe the docs are not good enough for that, but you can just run npx @spotlightjs/spotlight
1- serve the widget from the sidecar 2- add the CDN distro
Re: Spotlight: Sentry for Development
#49David 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.
Does this new package impact devtools source and initiators in a way where everything is attributed to spotlight?
Re: Spotlight: Sentry for Development
#50Earlier quoted context omitted.
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.
Isn't a tool that blocks all domains registered less than 30 days ago hugely annoying? I guess I can see the upside in terms of helping avoid newly registered phishing sites, but I don't think I could live with the downsides.
Frankly even most new things have older domains. (I know I'm not alone here in having domains registered for projects that may or may not ever materialise..!)
Also maybe worth saying that it's not even really about NextDNS as a tool, it's that block list or ones like it. I'm not sure if it's enabled by default or not.