Skip to content
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

"v8 version" or "llnode --version" #194

Open
mmarchini opened this issue May 8, 2018 · 4 comments · May be fixed by #431
Open

"v8 version" or "llnode --version" #194

mmarchini opened this issue May 8, 2018 · 4 comments · May be fixed by #431

Comments

@mmarchini
Copy link
Contributor

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.

@joyeecheung
Copy link
Member

Having an v8 version should be enough, --version of the llnode may just redirect the output to stdout somehow.

@joyeecheung
Copy link
Member

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
Copy link
Contributor Author

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.

@ghost
Copy link

ghost commented Aug 7, 2019

I was looking into this and trying to replace the version from package.json file but I am having difficulty to figure out from where, the message "lldb version X.X.X" is being outputted on the console when I run "llnode -v" etc.

vprab added a commit to vprab/llnode that referenced this issue Sep 30, 2023
@vprab vprab linked a pull request Sep 30, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants