@groovy.transform.CompileStatic class AsciidoctorJSExtension extends AbstractAsciidoctorJSExtension
Extension for configuring AsciidoctorJS. It can be used as both a project and a task extension.
| Modifiers | Name | Description |
|---|---|---|
static String |
NAME |
|
static PackageDescriptor |
PACKAGE_ASCIIDOCTOR |
| Constructor and description |
|---|
AsciidoctorJSExtension
(Project project)Attach extension to project. |
AsciidoctorJSExtension
(AbstractAsciidoctorNodeJSTask task)Attach extension to a task. |
| Type Params | Return Type | Name and description |
|---|---|---|
|
void |
clearRequires()Removes any previous requires. |
|
protected AsciidoctorJSModules |
createModulesConfiguration()Creates a new modules block. |
|
Configuration |
getConfiguration()A configuration containing all required NPM packages. |
|
Set<String> |
getRequires()Returns the set of NPM packages to be included except for the asciidoctor.js package. |
|
Provider<File> |
getToolingWorkDir()The suggested working directory that the implementation tool should use. |
|
void |
require(String name, String tag)Adds an additional NPM package that is required |
|
void |
require(String scope, String name, String tag)Adds an additional NPM package that is required |
|
void |
setVersion(Object v) |
| Methods inherited from class | Name |
|---|---|
class AbstractAsciidoctorJSExtension |
createModulesConfiguration, getConfiguration, getModules, getVersion, moduleVersion, modules, modules, setVersion |
Attach extension to project.
project - Project to attach to.Attach extension to a task.
task - Task to attach toRemoves any previous requires. If set on a task extension, no requires from global will be used.
Creates a new modules block.
A configuration containing all required NPM packages. The configuration will differ between global state and task state if the task has set different requires or different docbook versions.
asciidoctor.js.Returns the set of NPM packages to be included except for the asciidoctor.js package.
npm --require.The suggested working directory that the implementation tool should use. For instance if the implementation tool is Node.js with NPM, the directory will usually be the same for all tasks, but in cases where different versions of NPM packages are used by tasks then the working directory will be different for the specific task.
Adds an additional NPM package that is required
name - Name of packagetag - Tag of packageAdds an additional NPM package that is required
scope - Scope of packagename - Name of packagetag - Tag of packageCopyright © 2013-2024 the original author or authors. All rights reserved.