You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Curious, is there a way to correlate the version of node_modules/v8-profiler/build/profiler/vX/node-vY-linux-x64/profiler.node?
I notice that for v8 profiler version 5.7.0, I've seen different profiler.node versions depending on version of node.js running: v48 (for node 6.10.1, v51 for node 7.x, and I saw the profiler at runtime looking for v14 for I don't know what reason or version of node - as in this latter case the running node version should be 6.10.1).
This makes it tricky to deal with running the profiler across platforms and node versions if one isn't automatically doing npm install on each machine separately (say due to some legitimate reasons) but instead statically committing/storing the dependencies (as being pre-installed, that would work across machines/versions).
It would be great if there was a way to figure out what the proper Y version of profiler.node is for a given v8-profiler version X. And where one might be able to fetch that binary outside of npm install.
It would be less confusing if doing "npm install v8-profiler" actually pulled different versions for different node.js versions. But since they all seem to pull v5.7.0 but with different profiler.node binary (for different node.js versions, etc.) it does get confusing.
The text was updated successfully, but these errors were encountered:
Curious, is there a way to correlate the version of
node_modules/v8-profiler/build/profiler/vX/node-vY-linux-x64/profiler.node
?I notice that for v8 profiler version 5.7.0, I've seen different profiler.node versions depending on version of node.js running: v48 (for node 6.10.1, v51 for node 7.x, and I saw the profiler at runtime looking for v14 for I don't know what reason or version of node - as in this latter case the running node version should be 6.10.1).
This makes it tricky to deal with running the profiler across platforms and node versions if one isn't automatically doing npm install on each machine separately (say due to some legitimate reasons) but instead statically committing/storing the dependencies (as being pre-installed, that would work across machines/versions).
It would be great if there was a way to figure out what the proper Y version of profiler.node is for a given v8-profiler version X. And where one might be able to fetch that binary outside of npm install.
It would be less confusing if doing "npm install v8-profiler" actually pulled different versions for different node.js versions. But since they all seem to pull v5.7.0 but with different profiler.node binary (for different node.js versions, etc.) it does get confusing.
The text was updated successfully, but these errors were encountered: