Vitalii Akimov
Vitalii Akimov
In the current debugger implementation, the main thread is released on breakpoints. This way we can make other requests (such as some expressions evaluation, reloading sources etc). However, it is...
The partly changed functions can be reloaded with saving their state but the execution position and variable's positions are quite random (position based rather than better name based). So for...
During debugging it is highly unlikely all the functions from the application are called. To reduce compilation time the babel plugin on the first stage could just apply for closure...
Some expressions can be evaluated if they don't change the program state. This way, for example, in browser expression's results is immediately seen while we type it. This debugger can...
Now the debugger can only step into another explicit function calls. While there are many situations where an implicit function is called, it will be executed but the debugger cannot...
Expressions like `eval("var m = 10")` should add variable` into its parent scope. This doesn't work now (if the variable isn't already defined in that scope), because the variables are...
The local variables in the generated code are accessed by index, this won't work for `with` statement where the scope is dynamic. To solve this it needs to use runtime...
The generated code has almost no closure captured values, so it can be changed as a string in runtime and `eval`ed back. This way it can inline some operations depending...
Jest prevents typical node modules hacks for running instrumentations on import. This way the traspilation should be run through jest transform and so requires configuration. Instead it could apply similar...