Tobias Klein

This is step is only needed when you're still handling native modules as part of the build process. But since you're depending on system packages in your case the step...

Note that meanwhile I have commented on [an existing issue of node-prune](https://github.com/tj/node-prune/issues/63) to see if they can provide configurability, so that we don't need to use a fork any longer.

Good suggestions. Yes, I was also thinking to put this under the Bible browser box.

@zhuiks Note that I am considering to use web components for implementing this feature. However, I am not considering new CSS / JS libraries yet at this point.

I would prefer ODT as well, however at the time when I implemented the export I didn't find a decent JavaScript library for ODT/OpenDocument export. One thing, though. LibreOffice is...

Nice idea! Note that the presence of apocrypha is not available in the module meta data. We test for it. Doing that for all modules at once will come with...

Yeah, it's not properly documented at this point. I'll see whether I can add some instructions as well as look into the auto build option. You can have a peek...

Thanks for the proposal @Berovowilare. I am pretty sure the SWORD engine supports that ... and therefore it shouldn't be too hard to add it. I'll look into it one...

Yes, we could look into that. I can see how this might be useful. Something more solid would be an actual file export (exporting to a word document). The clipboard...

This could not be reproduced on Android 11 based on Chromium 103.0.5060.129. Cancelling a module installation works there.