-
Notifications
You must be signed in to change notification settings - Fork 9
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
Lazily loaded modules broke the require option for reveal.js #35
Comments
That's a good point, thanks! |
ggrossetie
added a commit
to ggrossetie/asciidoctor-cli.js
that referenced
this issue
Dec 2, 2018
ggrossetie
added a commit
that referenced
this issue
Apr 6, 2019
ggrossetie
added a commit
to ggrossetie/asciidoctor-cli.js
that referenced
this issue
Apr 6, 2019
ggrossetie
added a commit
to ggrossetie/asciidoctor-cli.js
that referenced
this issue
Apr 6, 2019
ggrossetie
added a commit
that referenced
this issue
Apr 6, 2019
resolves #35 automatically register converter and extension
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Due to the change we introduced in asciidoctor/asciidoctor-reveal.js#219, fixing issue asciidoctor/asciidoctor-reveal.js#205.
stacktrace:
This code is unreleased and the breaking behavior will be advertized in asciidoctor-reveal.js'. I just wanted to plug how to use
asciidoctor-cli.js
in the docs but stumbled upon the issue when testing.No rush, I can always document using asciidoctorjs cli later. It's nice btw. Since reveal.js is in Javascript, it simplifies deployment greatly. I'll probably start promoting this instead of the ruby back-end to colleagues.
The text was updated successfully, but these errors were encountered: