Why are so many software things written in node now? Seems that every new project I see, the installation begins with "npm install" :(
Spotlight: Sentry for Development
61–70 of 83 posts
Re: Spotlight: Sentry for Development
#62Why are so many software things written in node now? Seems that every new project I see, the installation begins with "npm install" :(
In this case it makes sense: it’s a UI widget. We wrote the proxy also in Node just because you already likely needed JavaScript to install the UI component that it felt logical.
Aside, 2019 and onward JavaScript has become the largest and fastest growing ecosystem of developers.
To others feedback though there’s no reason we should force you to take a bundler running in your UI. We’re gonna fix that quickly.
Re: Spotlight: Sentry for Development
#63Earlier quoted context omitted.
It basically leverages the Sentry SDKs during development and sends them into a local UI rather than a production Sentry instance. It also shows the data in a way that's more akin to local development.
When's it coming to Flask? :)
It works with it but it should be made more convenient. I will have a look :)
Re: Spotlight: Sentry for Development
#64David 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';
Also, I note the PHP SDK has gotten support for Spotlight - are there plans to do the same for the .NET SDK too?
Re: Spotlight: Sentry for Development
#65May 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...
Re: Spotlight: Sentry for Development
#66David 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…
[deleted]
Re: Spotlight: Sentry for Development
#67David 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…
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.
Re: Spotlight: Sentry for Development
#68Earlier quoted context omitted.
Does this new package impact devtools source and initiators in a way where everything is attributed to spotlight?
What’s an example concern? It shouldn’t anymore than Sentry already does
Mostly other devs seeing instrument.js everywhere in devtools vs. the actual source. The issue is for all envs and in development has been most problematic.
So obscuring console.log or network initiators the way Sentry currently does.
Webpack and bundlers seem to generally have this problem too. Sourcemaps help resolve when present in dev.
Re: Spotlight: Sentry for Development
#69May 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...
Your browser's dev tools don't show you what's happening inside your server (and any downstream services) when responding to the browser's HTTP requests. Spotlight does. That's what's special about it.
Re: Spotlight: Sentry for Development
#70May 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...
Why do you think they'd go away? As far as I'm aware all major browsers continue to add new functionality to their dev tools.