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
Today there's no easy way to get llnode's version, making it harder to report issues with detailed information. We could either have a llnode command v8 version or a command line argument --version reporting llnode's version, maybe showing LLDB's version as well.
Technically we could read package.json in the configuration scripts and compile the version numbers into the plugin...otherwise if we maintain something in the source code we could forget about updating it.
We use 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 :(
But I think reading from package.json might be feasible as well.
Activity
joyeecheung commentedon May 14, 2018
Having an
v8 versionshould be enough,--versionof thellnodemay just redirect the output to stdout somehow.joyeecheung commentedon May 14, 2018
Technically we could read package.json in the configuration scripts and compile the version numbers into the plugin...otherwise if we maintain something in the source code we could forget about updating it.
mmarchini commentedon May 14, 2018
We use 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 :(
But I think reading from package.json might be feasible as well.
Add "v8 version" subcommand to llnode