OurBigBook Docs
Install the NPM package globally and use it from the command line for a quick conversion:or to a file:You almost never want to do this except when developing OurBigBook, as it won't be clear what version of
npm install -g ourbigbook
printf 'ab\ncd\n' | ourbigbook --body-onlyprintf 'ab\ncd\n' | ourbigbook > tmp.htmlourbigbook the document should be compiled with. Just be a good infant and use OurBigBook with the template that contains a package.json via npx, OK?Furthermore, the default install of Chromium on Ubuntu 21.04 uses Snap and blocks access to dotfiles. For example, in a sane NVM install, our global CSS would live under One workaround is to use
/home/ciro/.nvm/versions/node/v14.17.0/lib/node_modules/ourbigbook/_obb/ourbigbook.css, which gets blocked because of the .nvm part:- forum.snapcraft.io/t/dot-files/7062
- bugs.launchpad.net/snapd/+bug/1607067
- superuser.com/questions/1546550/chromium-81-wont-display-dotfiles-anymore
- askubuntu.com/questions/1184357/why-cant-chromium-suddenly-access-any-partition-except-for-home
- askubuntu.com/questions/1214346/as-a-user-is-there-any-way-to-change-the-confinement-of-a-snap-package
--embed-resources, but this of course generates larger outputs.To run master globally from source for development see: Section "Run OurBigBook master". This one actually works despite the dotfile thing since your development path is normally outside of dotfiles.
Try out the JavaScript API with lib_hello.js:
npm install ourbigbook
./lib_hello.js