-
Notifications
You must be signed in to change notification settings - Fork 65
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
Make JS versions more inspectable #97
Comments
If we had a way to communicate back from the JavaScript to the kernel, this would be easier. |
Is there a way to generate files as part of the npm build step? |
Or maybe just something like console.logging the versions on load? |
It would be nice to if we don't have to add another build step to compile the versions into the python code. Logging the versions on load is trivial. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice to provide an easy means for the user to see what version of vega/vega-lite is installed with this package.
Currently (unless I'm mistaken) the only way is to look at package.json, find the vega-embed version, then go to the correct vega-embed release, open its package.json, and look for the vega-lite version there.
I'd love something similar to
The trick is to do that without too much manual bookkeeping...
The text was updated successfully, but these errors were encountered: