-
Notifications
You must be signed in to change notification settings - Fork 107
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
Upgrade to new WaveDrom #225
Comments
Would it be possible to provide an executable wrapper script for this? (see https://medium.com/netscape/a-guide-to-create-a-nodejs-command-line-package-c2166ad0452e for an example). The code is already searching for an executable file named Is there a way to query the version number via the CLI? That will be necessary so I can switch between the older and newer versions of wavedrom.
The asciidoctor extension currently reports PNG as a supported output format since the old version was able to produce this. The supported output formats are static at the moment in asciidoctor-diagram. The worst that will happen though is a runtime error if people request pngs with the newer version of wavedrom. |
Make sense. Will fix. |
I have published Generates SVG or PNG |
Perfect. Since the name of the command differs from the earlier version (was just |
I have a new version of wavedrom v2.1.2 here: https://github.com/wavedrom/wavedrom
it comes with browserless CLI. https://github.com/wavedrom/wavedrom/releases/tag/v2.1.2
It is a single file application and requires only
node.js
to run.node wavedrom.js -i sourceWaveDrom.json5 > result.svg
Current version can produce only
SVG
. Do we needPNG
?I can release
PNG
capable version, but that would require normalnpm install
flow.Originally posted by @drom in #190 (comment)
The text was updated successfully, but these errors were encountered: