If you're entering a breakpoint from a function called by the IIFE, you can just walk up the stack. If you're outside the IIFE entirely, I don't think it's possible The variables you're looking for may not even exist in memory, either before or after execution. Javascript doesn't have static variables like other languages do, so each time the IIFE is called, the variables inside it are thrown out. Javascript is also very much single-threaded (unless you use web workers and such, which come with limited interactivity with their parent pages) so unless you're trying to race-condition yourself with an async/await call, I don't think there's even a way to conceptually have these variables around in memory outside the IIFE scope.
You could (ab)use `var` to initialize the variable outside the IIFE scope so you can see the values produced by the last IIFE call.
You could (ab)use `var` to initialize the variable outside the IIFE scope so you can see the values produced by the last IIFE call.