Benedikt Meurer
Benedikt Meurer
Our current prototype solution looks roughly like this:  The *Language Component* part in DevTools front-end isn't separated as such, but rather tightly integrated with the *Source Mapping* at this...
@benjamingr "yes"!
It seems that most of this is concerned with making the `Proxy` constructor itself slower, which doesn't sound ideal either for many use cases. I'm also not 100% sure what...
@ljharb I can only speak for V8. But past experience tells us that important optimizations tend to spread into other JSVMs. For example inline caching (IC) is now in every...
/cc @hannespayer
cc @psmarshall
I suspect that this is a different problem than https://github.com/vitejs/vite/issues/13503. I think what we're seeing here is that the migration of the breakpoint is racing with the execution of the...
I just checked with Firefox 102.11.0esr (64-bit), which also misses the breakpoint. Bumping the timeout will likely make this more likely to work, but it'd still be flakily missing the...
One workaround that will always work: Put a `debugger` statement there instead of a breakpoint.
Notes from the meeting between Chrome DevTools and React folks, following up on the questions from @szuend. There are two separate use cases here: 1. To keep the async stack...