Lukas Stracke

@dcramer updated the description. We talked about this a while ago and said it'd be nice to have but didn't spend much time on it.

Hey @Shubhdeep12 I think this is overall still rather low-prio so I'd rather focus on other things for now (I'm giving a talk about Spotlight in the next days so...

Hey @TheAlexLichter thanks for writing in and sorry for the late reply! The preparation for Rolldown and rolldown-vite sounds all reasonable to me and like something we should do! >...

Thanks for answering! I'll backlog this with high prio for now but agree that we should get to it soon. (full transparency: we're a bit short-staffed at the moment and...

We so far only have two ideas and both are not ideal: - We add an SDK option, something like `readGlobalValues: boolean`, which defaults to `true` but you could opt...

> We could make it so that if you set release: undefined on init, then we don't read from the globals? Not a fan of making a difference between not...

Renaming was done via #15434, including the deprecation of `inboundFiltersIntegration`. Leaving this issue open and in the v10 milestone to remove the export with the old name.

woah completely forgot that this still exists. Re-running the tests for now. If localvariables still don't work, I think this is likely a limitation of `tsx` and something we can...

Update: - Updated test since some of the assertions were quite outdated by now - removed the LocalVariables test since I didn't get any local vars - Rebased and good...

Hey @edhgoose apologies for the late reply from our end! I think the problem here really is that we can't reproduce this (and as far as I understand, you can't...