node-machine-id can cause crashes

[Mike-Bell]

as per this issue, node-machine-id can cause problems on certain machines due to permissions issues: automation-stack/node-machine-id#56

This was made worse when this codebase changed from fetching the machine id during the report generation to fetching the machine id statically: 48e3bdc#diff-19c5769b32e486be5464e2b259d16fd1217d53501e90ea7ed95b4dce09e7a40dR13

This essentially means that importing this library will cause the consuming app to immediately crash for some users

[sbahra]

Thank you for reporting this! We will investigate and work on a fix.

[Mike-Bell]

This is pretty easy to repro if you disable access to your registry. I used method 2 here https://www.top-password.com/blog/3-ways-to-disable-registry-editor-in-windows/

[sbahra]

We'll have a patch out next week, we have a fix in a personal branch for testing.

[konraddysput]

Hey @sbahra @Mike-Bell

The new mechanism that we added to the backtrace-node@1.1.1 package should fix this issue. Thanks for sharing a lot of details with us @Mike-Bell. Please let us know if the newest version of the library doesn't help you.

Pull request reference: #37

Thanks!