asciidoctor.js
asciidoctor.js copied to clipboard
:scroll: A JavaScript port of Asciidoctor, a modern implementation of AsciiDoc
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@rollup/plugin-commonjs](https://togithub.com/rollup/plugins) | devDependencies | major | [`21.1.0` -> `22.0.2`](https://renovatebot.com/diffs/npm/@rollup%2fplugin-commonjs/21.1.0/22.0.2) | | [@types/node](https://togithub.com/DefinitelyTyped/DefinitelyTyped) |...
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@types/node](https://togithub.com/DefinitelyTyped/DefinitelyTyped) | devDependencies | patch | [`17.0.25` -> `17.0.45`](https://renovatebot.com/diffs/npm/@types%2fnode/17.0.25/17.0.45) | | [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/typescript-eslint) |...
I am trying out a pug template, for some reason, I can't get the toc to show up. Here are my .pug files: ``` [llu@llu pug-templates {asciidoctorjs_templates *}]$ cat document.html.pug...
Proposal: add a list of valid context names to the findBy docs. I've added all the names I've found so far. However, if this docs repo PR is accepted (https://github.com/asciidoctor/asciidoc-docs/pull/90),...
Is there any temporary solution to this? I am unable to use `@asciidoctor/core` with Svelte Code: ```svelte export let content; import Asciidoctor from '@asciidoctor/core'; const processor = Asciidoctor(); let rendered;...
We should refine exports as described in: https://nodejs.org/api/packages.html#packages_package_entry_points Currently, we define the following: ```json { "type": "module" "main": "dist/node/asciidoctor.js", "browser": "dist/browser/asciidoctor.js", "module": "dist/browser/asciidoctor.js", } ``` This is not good enough...
Say we have a root file with an include directive: ``` Root include::test.adoc[] ``` Then, the test file: ``` Test include::test2.adoc[opts=optional] ``` The expected result was just the text from...
https://docs.npmjs.com/cli/v7/using-npm/workspaces
Currently we are faking JavaScript environments for our tests but this is not ideal. I think we should create integration tests with the following technologies: * [Browserify](http://browserify.org/) * [Webpack](https://webpack.github.io/docs/) *...