-
Notifications
You must be signed in to change notification settings - Fork 188
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
resolves #143, Upgrade to Asciidoctor.js 1.5.6-preview.4 #156
Conversation
* Create a Rake task to generate a version of the Ruby converter which is compatible with Opal * Add asciidoctor.js as a dependency * Update HACKING and README accordingly
Why not pull the test I developed in #149 instead? |
I don't think tests should be part of the builder script but I like the idea of having "examples". |
Sure but first, I'm try to make sure I can have a working asciidoctor-reveal.js from javascript. |
Pulled in your branch on current master then ran:
It crashes with:
I'm trying from a clean directory using |
The converter task does not replace the generated file if it exists.
Run the clean task first and you should be fine.
Le 10 oct. 2017 11:43 PM, "Olivier Bilodeau" <[email protected]> a
écrit :
… Pulled in your branch on current master then ran:
bundle exec rake build:converter:opal
npm install # for the changed deps
npm run build
npm run test
It crashes with:
$ npm run test
> ***@***.*** test /home/olivier/src/asciidoc/asciidoctor-reveal.js
> node test/smoke.js
/home/olivier/src/asciidoc/asciidoctor-reveal.js/node_modules/opal-runtime/src/opal.js:4993
throw exception;
^
NotImplementedError: String#<< not supported. Mutable String methods are not supported in Opal.
at String.TMP_String_$lt$lt_1 [as $<<] (/home/olivier/src/asciidoc/asciidoctor-reveal.js/node_modules/opal-runtime/src/opal.js:20858:19)
at $Document.TMP_55 (/home/olivier/src/asciidoc/asciidoctor-reveal.js/dist/main.js:1933:20)
at $Document.$$instance_eval [as $instance_eval] (/home/olivier/src/asciidoc/asciidoctor-reveal.js/node_modules/opal-runtime/src/opal.js:3619:24)
at Opal.send (/home/olivier/src/asciidoc/asciidoctor-reveal.js/node_modules/opal-runtime/src/opal.js:1605:19)
at $Converter.$$document [as $document] (/home/olivier/src/asciidoc/asciidoctor-reveal.js/dist/main.js:1922:14)
at $Converter.$$__send__ [as $__send__] (/home/olivier/src/asciidoc/asciidoctor-reveal.js/node_modules/opal-runtime/src/opal.js:3546:21)
at Object.Opal.send (/home/olivier/src/asciidoc/asciidoctor-reveal.js/node_modules/opal-runtime/src/opal.js:1605:19)
at $Converter.alias [as $send] (/home/olivier/src/asciidoc/asciidoctor-reveal.js/node_modules/opal-runtime/src/opal.js:1779:19)
at $Converter.$$convert [as $convert] (/home/olivier/src/asciidoc/asciidoctor-reveal.js/dist/main.js:211:26)
at $Document.$$convert [as $convert] (/home/olivier/src/asciidoc/asciidoctor-reveal.js/node_modules/asciidoctor.js/dist/asciidoctor.js:27996:35)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ***@***.*** test: `node test/smoke.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ***@***.*** test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/olivier/.npm/_logs/2017-10-10T21_33_31_209Z-debug.log
I'm trying from a clean directory using npm i ../asciidoctor-reveal.js
and i'll report back. Still I expected smoke testing to work from inside
the repo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#156 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAUV3OsOnKAcy1UGqnFmEBxOVHtoq6k2ks5sq-TygaJpZM4Pxs4W>
.
|
@@ -261,6 +261,10 @@ Then run: | |||
$ gem push asciidoctor-revealjs-X.Y.Z.gem | |||
|
|||
. Check that the new version is available on https://rubygems.org/gems/asciidoctor-revealjs[rubygems.org] | |||
. Generate a compatible version of the Ruby converter (using opal mode) | |||
+ | |||
$ bundle exec rake build:converter:opal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A rake clean
is missing here but I think it should be done automatically whenever we build a template converter. Can you think of a reason why we shouldn't?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, the build task should always generate the file (even if it already exists) since we can generate the file using different modes.
Running |
This should be bumped to preview.4 |
The link does not point to a single line. Where do you want to bump the version ? |
As mentioned in #143 (comment) I will update the Rake task to follow @jirutka recommandation |
Sorry, I wasn't able to comment since it's not in the patch's context.
I would have done it but I had time to wait for your feedback on what you think of @jirutka's comments in #143 regarding the Rakefile and these I wanted to leave to you to decide upon |
@obilodeau Nice catch I totally missed it! 🤓 Also I think we should remove the section about Jade templates and help AsciidocFX migrate to the new version of the Reveal.js converter. Ping @rahmanusta 😉 |
This section is about doing pre-release testing. It was written when I was facing problems trying to reproduce an environment required to render slides before pushing the version to npm: https://github.com/asciidoctor/asciidoctor-reveal.js/blob/master/HACKING.adoc#test-a-local-asciidoctor-reveal-js-version. Issue #148 tries to explain the problem: The problem is when installing using npm and With the
Without it:
So for the README (or normal user) use case: no |
Interesting, I didn't know that 😐 Thank you for pointing that out, I will do some testing this morning 🐛 🔨 |
The behavior seems to have changed in npm 5+
https://github.com/npm/npm/releases/tag/v5.0.0 It's weird because it's a pretty big breaking change and they do not provide a clear alternative... or am I missing something ? For reference As a workaround, we could use |
I'm open to switching to
|
Thanks again for your help through this! |
Resolves #143
Ref #130