Incompatible with most recent node version?

[ghost]

Installing prepack on a recent node version (I tried v10.9.0 on a 4.18.5-arch1-1-ARCH Linux machine) fails; downgrading my node is, in my case, not an option.

I'm hit with the same error that was brought to our attention by @rpkoller back in June, and am afraid that v8-profiler, the dependency whose installation appears to be the cause of this issue, shows some maintenance issues.

They don't support node > 7 and seem to have had their last release over a year ago. Numerous issues were opened regarding this:

• node-pre-gyp ERR! Tried to download(404): https://node-inspector.s3.amazonaws.com/profiler/v5.7.0/node-v64-darwin-x64.tar.gz  node-inspector/v8-profiler#126
• Support node 10 node-inspector/v8-profiler#123
• v8-profiler doesn't work : Cannot find module './build/profiler/v5.7.0/node-v57-win32-ia32/profiler.node' node-inspector/v8-profiler#120
• Pre-built binaries not found for v8-profiler@5.7.0 and node@8.1.3 node-inspector/v8-profiler#114
• npm install v8-profiler - Doesn't work node-inspector/v8-profiler#104

but none of them have been addressed.

Is there anything you can do about this?

[hermanventer]

Is there another profiler with better support?

[ghost]

The v8 profiler in and of itself is fine; it's just the (seemingly unofficial?) node bindings that are causing these issues, i.e. the v8-profiler package.

Is there another profiler with better support?

I would reckon so. I just stumbled upon v8-profiler-node8, which (despite of its name) claims to also support node 10.x.

I tried to install it on my machine, and it built just fine. Maybe you could experiment with substituting the node bindings and see if it also works with your test matrix?

[hermanventer]

Great to hear. If you would like to put a pull request to do the substitution I would be happy to test it locally.

[NTillmann]

Fix has landed.