mary marchini

I usually recommend folks using nvm to install Node.js because installing packages globally just works with nvm without needing to run as root, and it always downloads Node.js from nodejs.org,...

You're still installing as root, which is not recommended by npm. If you must install as root, you might need some workaround, but I really recommend you don't install it...

Related change: https://github.com/v8/v8/commit/9a149afc28055e36b00e978b78ccb8f9acc15b60 (I should start to update our Node.js postmortem tests when I use new constants here :stuck_out_tongue: )

This seems related as well: https://chromium-review.googlesource.com/c/v8/v8/+/1278014

We use [bumpversion](https://github.com/peritus/bumpversion) here at Sthima to easily bump versions in our projects. It is a Python tool though, and I'm not aware of any similar tool for Node.js :(...

I think JavaScript developers will expect `getProcessObject` to return Node.js' process object for the core dump instead of a `SBObject` representation. Maybe we could have lldb-related methods inside a `LLDB`...

> > I think JavaScript developers will expect getProcessObject to return Node.js' process object for the core dump > > Is it even possible to recreate that? process is fairly...

Oh, nice catch. There was a typo on the Shields URL (`push` instead of `on%20push%20or%20pull_request`). Do you mind updating the URL to keep using shield (so that all three badges...

Interesting, the type of those fields didn't change, but they are all prefixed by `__int`. Is the metadata generated for Torque classes prefixed by the the metadata type instead of...

`class_Symbol__name__Object` was removed as well, I'm guessing in this version. Still investigating.