-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm install v8-profiler
fails with node v7.0.0 on osx
#98
Comments
#96 looks like it would fix this |
Same issue with node-pre-gyp build for electron v1.4.6 |
Hi folks, We have a good tool that generates flamegraph and do some profiling things, and that tool is using v8-profiler, and we can't test against Node.js 7x yet :/ thanks. |
So has this package been abandoned? @3y3 This has been broken for a long time. |
is there any offical solution? |
@suntopo we've switched to the fork from @RisingStack which works on Node 4 to 7
|
can we get the fix applied here too please? master...RisingStack:master |
Still no update? |
@sontek we've switched to the fork from @RisingStack which works on Node 4 to 7 "@risingstack/v8-profiler": "^5.7.0" |
@helio-frota Yeah, I'd like to do that as well but I'm actually looking to use https://github.com/node-inspector/node-inspector but it depends on |
Please try |
@hustxiaoc I am getting: "Error: Cannot find module './build/profiler/v5.7.0/node-v51-darwin-x64/profiler.node' on 5.7.0 The NPM still seems to ship node-v48-darwin-x64. |
I used:
|
The same problem
https://gist.github.com/dilame/3e6aba9c9a9ab92a1a1f1ee2acb2bfee |
Hi, I got the similar problem. I uninstalled v8-profiler and used node v6.11.4 using nvm then installed v8-profiler again. Problem solved. |
@tankala u're downgrading stuff, won't work for long. v8-profiler v8-debug... are dead! |
@datdinhquoc : Not downgrading. What I meant to say is you have multiple node versions installed in your server/system. You need to make sure which node version you are using at the time of module install and at the time of running the application |
@tankala that sounds like a workaround, yeah, npm install with node 6, then run with node 8 or 10. hope it works without any incompatibilities |
Same on node v10 |
This one is installing https://www.npmjs.com/package/v8-profiler-node8 |
worked for me. I had to explicitly specify the version |
The text was updated successfully, but these errors were encountered: