mary marchini
mary marchini
As title says
We have linter for our source code, but not for tests. Would be nice to have linter for tests as well.
Today there's no easy way to get llnode's version, making it harder to report issues with detailed information. We could either have a llnode command `v8 version` or a command...
Our install script tries to fetch branch `release_71` from `llvm-mirror/lldb`, but this branch doesn't exist (there's a `release_70` though).
V8 stopped using JSArrays to store the stack in https://chromium-review.googlesource.com/c/v8/v8/+/1564060. Now the stack is stored in a raw FixedArray. We'll need to change our heuristics to handle this.
- [ ] `v8 findrefs` equivalent - List of retainers as a property of heap instances? - [x] ~`v8 bt` equivalent~ - Accessible through `LLNode.getProcessObject().threads[0]` - [ ] `v8 getactivehandles`...
tl;dr: I think we should standarize the output for all types into JSON format. The default output should hide V8 implementation details and should only show properties and elements accessible...
The first time we run `v8 findjsobjects` can be very slow. Maybe there's nothing we can do about it, but I think we can try to make it faster (at...
Thinking about the usability of llnode for JavaScript developers, showing native calls and memory addresses can be intimidating. Maybe we could have a JavaScript-only mode, which shows objects by an...