Boshen
Boshen
Ahh I accidentally clicked merged, @overlookmotel please review despite being merged.
> In my opinion, this functionality should be prioritized after ES2015 (? not sure). Implementing this would unblock a lot of things, for example `oxc-jest`. > perhaps we could simply...
> I mean the order of transforming, the current order is x0_, x1_, etc. I think it should be after the currently last (ES2015)? Yes it should be the last...
no-undef is still under nurser, PRs welcome! The fix should be checking for symbol flags.
Let me double check how the resolver interacts with the language server.
High memory usage is associated with the mis-use of the resolver, we are getting it fixed in * https://github.com/oxc-project/oxc/pull/12016 We will continue tracing the memory leak after the above change.
Are there any noticeable memory issues in recent versions?
There are a few remaining issues but we'll close this issue for house keeping.
We won't be needing `visit_span` once we have AST node id for this particular use case. Close as not planned.
Will reopen when planned.