@asyncapi/generator 2.8.4 → 3.0.0

package/CHANGELOG.md

@@ -1,5 +1,44 @@
 # @asyncapi/generator
 
+## 3.0.0
+
+### Major Changes
+
+- df08ae7: ### Breaking Changes
+
+  - You must use Node.js 24.11 or higher, and NPM 11.5.1 or higher
+  - Nunjucks renderer removed — React is now the sole rendering engine. No need to specify render engine in config anymore
+  - Nunjucks filters package and its public filters removed; filter-based template APIs no longer available.
+  - `ag` CLI is no longer available. It was announced some time ago that it would be deprecated, and users are encouraged to switch to the [AsyncAPI CLI](https://github.com/asyncapi/cli/)
+
+  ### Migration Guides
+
+  - [Migrating from Nunjucks to React render engine](https://github.com/asyncapi/generator/blob/%40asyncapi/generator%402.8.4/apps/generator/docs/migration-nunjucks-react.md)
+  - [Migrating from `ag` CLI to AsyncAPI CLI](https://github.com/asyncapi/generator/blob/%40asyncapi/generator%402.8.4/apps/generator/docs/migration-cli.md)
+
+### Patch Changes
+
+- Updated dependencies [df08ae7]
+  - @asyncapi/generator-helpers@1.0.0
+
+## 2.11.0
+
+### Minor Changes
+
+- ced1404: Pushing of release https://github.com/asyncapi/generator/pull/1747 that failed due to pipeline issues.
+
+## 2.10.0
+
+### Minor Changes
+
+- aee45ba: Pushing of release https://github.com/asyncapi/generator/pull/1747 that failed due to pipeline issues.
+
+## 2.9.0
+
+### Minor Changes
+
+- 8168bcd: Pushing of release https://github.com/asyncapi/generator/pull/1747 that failed due to pipeline issues.
+
 ## 2.8.4
 
 ### Patch Changes

package/docs/api.md

@@ -8,7 +8,6 @@ Reference API documentation for AsyncAPI Generator library.
 
 <dl>
 <dt><a href="#Generator">Generator</a></dt>
-<dd></dd>
 </dl>
 
 ## Members
@@ -16,7 +15,7 @@ Reference API documentation for AsyncAPI Generator library.
 <dl>
 <dt><a href="#listBakedInTemplates">listBakedInTemplates</a> ⇒ <code>Array.&lt;Object&gt;</code></dt>
 <dd><p>List core templates, optionally filter by type, stack, protocol, or target.
-Use name of returned templates as input for the <code>generate</code> method for template generation. Such core templates code is part of the @asyncapi/generator package.</p></dd>
+Use name of returned templates as input for the `generate` method for template generation. Such core templates code is part of the @asyncapi/generator package.</p></dd>
 </dl>
 
 
@@ -54,7 +53,6 @@ Use name of returned templates as input for the <code>generate</code> method for
         * [.executeAfterHook()](#Generator+executeAfterHook) ⇒ `Promise.<void>`
         * [.parseInput()](#Generator+parseInput)
         * [.configureTemplate()](#Generator+configureTemplate)
-        * ~~[.generateFromString(asyncapiString, [parseOptions])](#Generator+generateFromString) ⇒ `Promise.<(TemplateRenderResult|undefined)>`~~
         * [.generateFromURL(asyncapiURL)](#Generator+generateFromURL) ⇒ `Promise.<(TemplateRenderResult|undefined)>`
         * [.generateFromFile(asyncapiFile)](#Generator+generateFromFile) ⇒ `Promise.<(TemplateRenderResult|undefined)>`
         * [.installTemplate([force])](#Generator+installTemplate)
@@ -367,57 +365,10 @@ Parse the generator input based on the template `templateConfig.apiVersion` valu
 <a name="Generator+configureTemplate"></a>
 
 * generator.configureTemplate()** :
-Configure the templates based the desired renderer.
+Configure the templates.
 
 **Kind**: instance method of [`Generator`](#Generator)  
 
-<a name="Generator+generateFromString"></a>
-
-### ~~generator.generateFromString~~
-***Deprecated***
-
-Generates files from a given template and AsyncAPI string.
-
-**Kind**: instance method of [`Generator`](#Generator)  
-**Params**
-
-- asyncapiString `String` - AsyncAPI string to use as source.
-- [parseOptions] `Object` ` = {}` - AsyncAPI Parser parse options. Check out [@asyncapi/parser](https://www.github.com/asyncapi/parser-js) for more information.
-
-**Example**  
-```js
-const asyncapiString = `
-asyncapi: '2.0.0'
-info:
-  title: Example
-  version: 1.0.0
-...
-`;
-generator
-  .generateFromString(asyncapiString)
-  .then(() => {
-    console.log('Done!');
-  })
-  .catch(console.error);
-```
-**Example** *(Using async/await)*  
-```js
-const asyncapiString = `
-asyncapi: '2.0.0'
-info:
-  title: Example
-  version: 1.0.0
-...
-`;
-
-try {
-  await generator.generateFromString(asyncapiString);
-  console.log('Done!');
-} catch (e) {
-  console.error(e);
-}
-```
-
 <a name="Generator+generateFromURL"></a>
 
 ### generator.generateFromURL

package/docs/asyncapi-document.md

@@ -21,7 +21,7 @@ In the following sections, you'll learn about the inner working of the generator
 3. The **Parser** validates the **AsyncAPI Document** using additional schema-related plugins, either the OpenAPI schema, RAML data types, or Avro schema.
 4. If the **Parser** determines that the **AsyncAPI Document** is valid, it manipulates the original JSON/YAML document and provides a set of helper functions in return, bundling them together into an **asyncapi** variable that is an instance of [**AsyncAPIDocument**](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#asyncapidocument).
 5. At this point, the **Generator** passes the **originalAsyncAPI** and the **asyncapi** which make up part of the **[Template Context](template-context)** to the **Render Engine**.
-6. The **Template Context** is accessible to the template files that are passed to either the [react](react-render-engine) or [nunjucks](nunjucks-render-engine) **Render Engines**.
+6. The **Template Context** is accessible to the template files that are passed to the [react](react-render-engine) **Render Engine**.
 
 ```mermaid
 graph LR

package/docs/configuration-file.md

@@ -21,7 +21,6 @@ metadata:
   target: javascript
   stack: express
 
-renderer: react
 apiVersion: v3
 supportedProtocols:
   - amqp
@@ -86,7 +85,6 @@ Alternatively, you can include your configuration in the `generator` property of
     "target": "javascript",
     "stack": "express"
   },
-  "renderer": "react",
   "apiVersion": "v3",
   "supportedProtocols": ["amqp", "mqtt"],
   "parameters": {
@@ -150,7 +148,6 @@ The `generator` property from `package.json` file must contain a JSON object and
 | `metadata.protocol` | String | **Required for `client`/`sdk`**. The protocol this template targets (e.g., `websocket`, `kafka`). Not used for `docs`/`config`. |
 | `metadata.target` | String | **Required**. The output language or format (e.g., `javascript`, `html`, `yaml`). |
 | `metadata.stack` | String | Optional. The stack or framework (e.g., `express`, `quarkus`). Only for `client`/`sdk`. |
-| `renderer` | String | Its value can be either `react` or `nunjucks` (default). |
 | `apiVersion` | String | Determines which **major** version of the [Parser-API](https://github.com/asyncapi/parser-api) the template uses. For example, `v2` for `v2.x.x`. If not specified, the Generator assumes the template is not compatible with the Parser-API so it will use the [Parser-JS v1 API](https://github.com/asyncapi/parser-js/tree/v1.18.1#api-documentation). For templates that need to support AsyncAPI specification v3 make sure to use `v3` [Parser-API](https://github.com/asyncapi/parser-api). If the template uses a version of the Parser-API that is not supported by the Generator, the Generator will throw an error. |
 | `supportedProtocols` | [String] | A list with all the protocols this template supports. |
 | `parameters` | Object[String, Object] | An object with all the parameters that can be passed when generating the template. When using the command line, it's done by indicating `--param name=value` or `-p name=value`. |
@@ -166,7 +163,6 @@ The `generator` property from `package.json` file must contain a JSON object and
 | `conditionalGeneration[filePath/directoryName].validation` | Object (JSON Schema fragment) | The validation defines the condition under which the file or directory will be generated. It must be a valid JSON Schema fragment that validates the value of the parameter. For example, if you want to include a folder only when includeDocs is true, use "validation": `{ "const": true }`. You can also use more complex validation logic, like "enum": ["yes", "true"] or "type": "string" with a "pattern" constraint. If the parameter fails validation, the file or folder will not be included in the generated output. This allows for powerful and flexible control over template generation based on user input. |
 | `nonRenderableFiles` | [String] | A list of file paths or [globs](https://en.wikipedia.org/wiki/Glob_(programming)) that must be copied "as-is" to the target directory, i.e., without performing any rendering process. This is useful when you want to copy binary files. |
 | `generator` | [String] | A string representing the generator version-range the template is compatible with. This value must follow the [semver](https://nodejs.dev/learn/semantic-versioning-using-npm) syntax. E.g., `>=1.0.0`, `>=1.0.0 <=2.0.0`, `~1.0.0`, `^1.0.0`, `1.0.0`, etc. [Read more about semver](https://docs.npmjs.com/about-semantic-versioning). |
-| `filters` | [String] | A list of modules containing functions that can be used as Nunjucks filters. In case of external modules, remember they need to be added as a dependency in `package.json` of your template. |
 | `hooks` | Object[String, String] or Object[String, Array[String]] | A list of modules containing hooks, except for the ones you keep locally in your template in the default location. For each module you must specify the exact name of the hook that should be used in the template. For a single hook, you can specify it as a string; for more hooks, you must pass an array of strings. In the case of external modules, remember they need to be added as a dependency in `package.json` of your template. There is also [an official hooks library](hooks#official-library) always included in the generator. As this is a library of multiple hooks, you still need to explicitly specify in the configuration which one you want to use. Use `@asyncapi/generator-hooks` as the library name. |
 
 ## Special parameters

package/docs/file-templates.md

@@ -3,67 +3,9 @@ title: "File templates"
 weight: 140
 ---
 
-## Generating files with the Nunjucks render engine
-
-> **Note**: This section applies only to the Nunjucks render engine. For information on using the React render engine, refer to the [Generating files with the React render engine](#generating-files-with-the-react-render-engine) section below.
-
-> **Note**: Nunjucks renderer engine is deprecated and will be removed in the future. Use the React renderer engine instead. For more details read notes from release [@asyncapi/generator@2.6.0](https://github.com/asyncapi/generator/releases/tag/%40asyncapi%2Fgenerator%402.6.0).
-
-It is possible to generate files for each specific object in your AsyncAPI documentation using the Nunjucks render engine. For example, you can specify a filename like `$$channel$$.js` to generate a file for each channel defined in your AsyncAPI. The following file-template names and extra variables are available:
-
-   - `$$channel$$`, within the template-file you have access to two variables [`channel`](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#channel) and [`channelName`](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#channels). Where the `channel` contains the current channel being rendered.
-   - `$$message$$`, within the template-file you have access to two variables [`message`](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#message) and [`messageName`](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#message). Where `message` contains the current message being rendered.
-   - `$$schema$$`, within the template-file you have access to two variables [`schema`](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#schema) and [`schemaName`](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#schema). Where `schema` contains the current schema being rendered. Only schemas from [Components object](https://www.asyncapi.com/docs/reference/specification/latest#componentsObject) are used. 
-   - `$$everySchema$$`, within the template-file you have access to two variables [`schema`](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#schema) and [`schemaName`](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#schemas). Where `schema` contains the current schema being rendered. Every [Schema object](https://www.asyncapi.com/docs/specifications/2.0.0/#schemaObject) from the entire AsyncAPI file is used.
-   - `$$objectSchema$$`, within the template-file you have access to two variables [`schema`](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#schema) and [`schemaName`](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#schemas). Where `schema` contains the current schema being rendered. All the [Schema objects](https://www.asyncapi.com/docs/reference/specification/latest#multiFormatSchemaObject) with type object is used.
-   - `$$parameter$$`, within the template-file you have access to two variables [`parameter`](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#channelparameter) and [`parameterName`](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#channelparameters). Where the `parameter` contains the current parameter being rendered.
-   - `$$securityScheme$$`, within the template-file you have access to two variables [`securityScheme`](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#securityscheme) and [`securitySchemeName`](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#securityschemes). Where `securityScheme` contains the current security scheme being rendered.
-
-The file name will be equal to `*Name` variable.
-
-### Example
-
-The file name is `$$schema$$.txt`, the content of this file is:
-```
-Schema name is '{{schemaName}}' and properties are:
-{% for propName, prop in schema.properties() %}
-- {{prop.uid()}}
-{% endfor %}
-```
-
-With the following AsyncAPI:
-```
-components:
-  schemas: 
-    peoplePayload:
-      type: object
-      properties:
-        event:
-          $ref: "#/components/schemas/people"
-    people:
-      type: object
-      properties:
-        id:
-          type: integer
-```
-
-The generator creates two files `peoplePayload.txt` and `people.txt` with the following content:
-```
-Schema name is 'peoplePayload' and properties are:
-- people
-```
-
-and
-```
-Schema name is 'people' and properties are:
-- id
-```
-
-> You can see an example of a file template that uses the Nunjucks render engine [here](https://github.com/asyncapi/template-for-generator-templates/tree/nunjucks/template/schemas).
-
 ## Generating files with the React render engine
 
-The above method of rendering **file templates** only works for the Nunjucks render engine. To use the React render engine, you need to follow a different approach. The React render engine allows for a more generic way to render multiple files by returning an array of `File` components in the rendering component. This can be particularly useful for complex templates or when you need to generate a large number of files with varying content.
+The React render engine allows for a more generic way to render multiple files by returning an array of `File` components in the rendering component. This can be particularly useful for complex templates or when you need to generate a large number of files with varying content.
 
 ### Example 1: Rendering hardcoded files
 

package/docs/generator-template-java.md

@@ -61,7 +61,6 @@ Add the following code snippet to your package.json file:
     "version": "0.0.1",
     "description": "A template that generates a Java MQTT client using MQTT.",
     "generator": {
-      "renderer": "react",
       "apiVersion": "v1",
       "generator": ">=1.10.0 <2.0.0",
       "supportedProtocols": ["mqtt"]
@@ -287,7 +286,6 @@ In **package.json** define a script property that you invoke by calling `npm run
     "version": "0.0.1",
     "description": "A template that generates a Java MQTT client using MQTT.",
     "generator": {
-      "renderer": "react",
       "apiVersion": "v1",
       "generator": ">=1.10.0 <2.0.0",
       "supportedProtocols": ["mqtt"],

package/docs/generator-template.md

@@ -112,7 +112,6 @@ The **package.json** file is used to define the dependencies for your template.
   "version": "0.0.1",
   "description": "A template that generates a Python MQTT client using MQTT.",
   "generator": {
-    "renderer": "react",
     "apiVersion": "v1",
     "generator": ">=1.10.0 <2.0.0",
     "supportedProtocols": ["mqtt"]
@@ -132,7 +131,6 @@ Here's what is contained in the code snippet above:
 - **version** - the current version of your template.
 - **description** - a description of what your template does.
 - **generator** - specify generator [specific configuration](https://www.asyncapi.com/docs/tools/generator/configuration-file).
-  - **renderer** - can either be [`react`](https://www.asyncapi.com/docs/tools/generator/react-render-engine) or [`nunjucks`](https://www.asyncapi.com/docs/tools/generator/nunjucks-render-engine). In this case the generator will pass your template to the react render engine to generate the output.
   - **apiVersion** - specifies which major version of the [Parser-API](https://github.com/asyncapi/parser-api) your template will use.
   - **generator** - a string representing the generator version-range your template is compatible with.
   - **supportedProtocols** - A list that specifies which protocols are supported by your template.
@@ -328,7 +326,6 @@ In **package.json** you can have the scripts property that you invoke by calling
         "test": "npm run test:clean && npm run test:generate && npm run test:start"
       },
       "generator": {
-        "renderer": "react",
         "apiVersion": "v1",
         "generator": ">=1.10.0 <2.0.0",
         "supportedProtocols": ["mqtt"]
@@ -459,7 +456,7 @@ export default function ({ asyncapi, params }) {
 4. Dynamically get the class name **TemperatureServiceClient** from the AsyncAPI document from the **info** object using the Parser API using the code: `asyncapi.info().title()` . It will return `Temperature Service`, then remove the spaces and add `Client` as a suffix.
 5. There is no templating needed in the `__init__` function, there is only hardcoded information.
 
-> If you're on the fence about which templating engine you should use in your template, check out the [React render engine](https://www.asyncapi.com/docs/tools/generator/react-render-engine) and [nunjucks render engine](https://www.asyncapi.com/docs/tools/generator/nunjucks-render-engine) documentation.
+> If you're on the fence about which templating engine you should use in your template, check out the [React render engine](https://www.asyncapi.com/docs/tools/generator/react-render-engine) documentation.
 In the next section, you'll refactor your template to use React.
 
 #### 5c. Creating a reusable component

package/docs/index.md

@@ -24,8 +24,8 @@ The AsyncAPI generator is a tool that generates anything you want using the **[A
 3. The **Parser** uses additional plugins such as the OpenAPI, RAML, or Avro schemas to validate custom schemas of message payloads defined in the **AsyncAPI Document**.
 4. If the **Parser** determines that the original **AsyncAPI Document** is valid, it manipulates the document and returns a set of helper functions and properties and bundles them together into an **asyncapi** variable that is an instance of [**AsyncAPIDocument**](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#asyncapidocument). The **asyncapi** helper functions make it easier to access the contents of the AsyncAPI Document.
 5. At this point, the **Generator** passes the **[asyncapi](generator/asyncapi-document#method-2-asyncapi-and-template)**, the **[originalAsyncAPI](generator/asyncapi-document#method-1-originalasyncapi-and-template)**, and the **params** which collectively make up the **[Template Context](generator/template-context)** to the **Render Engine**. 
-6. AsyncAPI has two **Render Engines**([react](generator/react-render-engine) and [nunjucks](generator/nunjucks-render-engine)). Depending on which one you've specified in your `package.json`, the **Generator** knows the right **Render Engine** to pass both the **Template Files** and the **Template Context**.
-7. Once the **Render Engine** receives the **Template Files** and the **Template Context**, it injects all the dynamic values in your react or nunjucks based **Template Files** using the **Template Context**. As a result, the **Render Engine** generates **markdown**, **pdf**, **boilerplate code**, and **anything else** you specified to be generated as output.
+6. AsyncAPI has a **Render Engine**([react](generator/react-render-engine)). The **Generator** passes both the **Template Files** and the **Template Context** to the **Render Engine**.
+7. Once the **Render Engine** receives the **Template Files** and the **Template Context**, it injects all the dynamic values in your react based **Template Files** using the **Template Context**. As a result, the **Render Engine** generates **markdown**, **pdf**, **boilerplate code**, and **anything else** you specified to be generated as output.
 
 > You can generate anything you want using the generator as long as it can be defined in a **Template**.
 

package/docs/jsdoc2md-handlebars/main-index/global-index/global-index-dl.hbs

@@ -0,0 +1,13 @@
+{{#globals kind=kind ~}}
+{{#if @first~}}{{>heading-indent}}{{../title}}
+
+<dl>
+{{/if~}}
+<dt>{{>sig-link-html}}</dt>
+{{#if description~}}
+<dd><p>{{{inlineLinks description}}}</p></dd>
+{{/if}}
+{{#if @last~}}</dl>
+
+{{/if~}}
+{{/globals~}}

package/docs/jsdoc2md-handlebars/member-index-grouped.hbs

@@ -0,0 +1,6 @@
+{{#unless deprecated~}}
+{{string-repeat "    " (add level baseLevel)}}* {{#unless (equal _title undefined)}}_{{_title}}_{{else}}{{>sig-link}}{{/unless}}
+{{#groupBy (option "group-by")~}}
+{{>member-index-grouped baseLevel=(add ../level ../baseLevel 1)~}}
+{{/groupBy~}}
+{{/unless~}}

package/docs/jsdoc2md-handlebars/member-index-list.hbs

@@ -0,0 +1,6 @@
+{{#unless deprecated~}}
+{{>index-indent}}* {{>sig-link-parent}}
+{{#indexChildren ~}}
+{{>member-index-list~}}
+{{/indexChildren}}
+{{/unless~}}

package/docs/jsdoc2md-handlebars/members.hbs

@@ -0,0 +1 @@
+{{#children inherited=undefined ~}}{{#unless deprecated~}}{{>docs~}}{{/unless~}}{{/children~}}

package/docs/react-render-engine.md

@@ -3,14 +3,14 @@ title: "React render engine"
 weight: 110
 ---
 
-[React](https://reactjs.org) is the render engine that we strongly suggest you should use for any new templates. The only reason it is not the default render engine is to stay backward compatible.
+[React](https://reactjs.org) is the only  render engine supported by the AsyncAPI generator.
 
-* It enables the possibility of [debugging](#debugging-react-template) your template (this is not possible with Nunjucks).
+* It enables the possibility of debugging your template.
 * It provides better error stack traces.
 * Provides better support for separating code into more manageable chunks/components.
-* The readability of the template is much better compared to Nunjucks syntax.
+* The readability of the template is much better.
 * Better tool support for development.
-* Introduces testability of components which is not possible with Nunjucks.
+* Introduces testability of components.
 
 When writing React templates you decide whether to use CommonJS, ES5, or ES6 modules since everything is bundled together before the rendering process takes over. We use our own React renderer which can be found in the [Generator React SDK](https://github.com/asyncapi/generator-react-sdk). 
 There you can find information about how the renderer works or how we transpile your template files.
@@ -45,36 +45,4 @@ For further information about components, props, etc, see the [Generator React S
    - `asyncapi` which is a parsed spec file object. Read the [API](https://github.com/asyncapi/parser-api/blob/master/docs/api.md#asyncapidocument) of the Parser to understand what structure you have access to in this parameter.
    - `originalAsyncAPI` which is an original spec file before it is parsed. 
    - `params` that contain the parameters provided when generating.
-1. All the file templates are supported where the variables are provided after the default props as listed above. 
-
-### Debugging React template in VSCode
-
-With React, it enables you to debug your templates. For Visual Studio Code, we have created a boilerplate [launch configuration](https://code.visualstudio.com/docs/editor/debugging#_launch-configurations) to enable debugging in your template. Add the following launch configuration:
-
-```json
-{
-  "version": "0.2.0",
-  "configurations": [
-    {
-      "type": "node",
-      "request": "launch",
-      "name": "Debug template",
-      "timeout": 10000,
-      "sourceMaps": true,
-      "args": [
-        "./asyncapi.yml",
-        "./template",
-        "--output",
-        "./output",
-        "--install",
-        "--force-write"
-      ],
-      "program": "ag"
-    }
-  ]
-}
-```
-
-Now replace `./asyncapi.yml` with your document of choice. Replace `./template` with the path to your React template. You can now debug your template by adding any breakpoints you want and inspecting your code.
-
-
+1. All the file templates are supported where the variables are provided after the default props as listed above. 

package/docs/template-development.md

@@ -3,7 +3,7 @@ title: "Template development"
 weight: 80
 ---
 > **Note**
-> It is advised against attempting to manually template types and models from scratch using the AsyncAPI templating engines such as Nunjucks and React render engines. Instead, it is recommended to use [AsyncAPI Modelina](/docs/tools/generator/model-generation) a dedicated library for model generation.
+> It is advised against attempting to manually template types and models from scratch using the AsyncAPI templating engines such as the React render engine. Instead, it is recommended to use [AsyncAPI Modelina](/docs/tools/generator/model-generation) a dedicated library for model generation.
 
 ## Minimum template requirements
 
@@ -40,9 +40,7 @@ The following block shows an example `package.json` file that points to the [Rea
 ```json
 {
   "name": "myTemplate",
-  "generator": {
-    "renderer": "react"
-  },
+  "generator": {},
   "dependencies": {
     "@asyncapi/generator-react-sdk": "^0.2.25"
   }
@@ -57,7 +55,6 @@ You must configure the generator's `package.json` file to contain JSON objects w
 
 |Name|Type|Description|
 |---|---|---|
-|`renderer`| String | Its value can be either `react` or `nunjucks` (default).
 |`supportedProtocols`| [String] | A list with all the protocols this template supports.
 |`parameters`| Object[String, Object] | An object with all the parameters that can be passed when generating the template. When using the command line, it's done by indicating `--param name=value` or `-p name=value`.
 |`parameters[param].description`| String | A user-friendly description about the parameter.
@@ -76,7 +73,6 @@ The following examples show some advanced configurations that we can use in our
 {
   "name": "myTemplate",
   "generator": {
-    "renderer": "react",
     "supportedProtocols": [
       "mqtt"
     ]
@@ -98,7 +94,6 @@ Additionally, we can also have a configuration called `parameters`, which is an
 {
   "name": "myTemplate",
   "generator": {
-    "renderer": "react",
     "supportedProtocols": [
       "mqtt"
     ],

package/docs/template.md

@@ -45,8 +45,8 @@ You can store template projects on a local drive or as a `git` repository during
 2. **asyncapi** (which is an instance of AsyncAPIDocument) is injected into your template file by default.
 3. **params** are the parameters you pass to the AsyncAPI CLI. Later, you can also pass these **params** further to other components. 
 4. The generator passes both the **asyncapi**, the **originalAsyncAPI**, and the **params** to the **Template Context**.
-5. Concurrently, the generator passes **Template files** to the **Render engine** as well. AsyncAPI uses two render engines — _react_ and _nunjucks_.
-6. Once the Render Engine receives both the Template Files and the Template Context, it injects all the dynamic values into your react or nunjucks engine, based on the Template Files using the Template Context.
+5. Concurrently, the generator passes **Template files** to the **Render engine** as well. AsyncAPI uses the _react_ render engine.
+6. Once the Render Engine receives both the Template Files and the Template Context, it injects all the dynamic values into your react based Template Files using the Template Context.
 7. The render engine generates whatever output you may have specified in your template. (i.e. code, documentation, diagrams, pdfs, applications, etc.)
 
 ```mermaid

package/docs/typescript-support.md

@@ -3,11 +3,9 @@ title: "TypeScript support"
 weight: 150
 ---
 
-The AsyncAPI generator has TypeScript support for [hooks](#hooks) and Nunjucks's [filters](#filters). Assumptions:
+The AsyncAPI generator has TypeScript support for [hooks](hooks). Assumptions:
 
-- Installing the `typescript` package and creating the` tsconfig.json` file isn't necessary.
+- Installing the `typescript` package and creating the `tsconfig.json` file isn't necessary.
 - Source code of the hook/filter must have `.ts` extension.
 - Each package related to the typings for TypeScript like `@types/node` must be installed in the template under `dependencies` array. This is because the Generator transpiles the TypeScript code on-the-fly while rendering the template, and cannot use packages under `devDependencies`.
-- Each template should have `@types/node` package installed to enable support for typings for Node.
-
-
+- Each template should have `@types/node` package installed to enable support for typings for Node.

package/jest.config.js

@@ -1,9 +1,6 @@
-const path = require('path');
+const baseConfig = require('../../jest.config.base');
+
 module.exports = {
+  ...baseConfig(__dirname),
   clearMocks: true,
-  moduleNameMapper: {
-    '^nimma/legacy$': '<rootDir>../../node_modules/nimma/dist/legacy/cjs/index.js',
-    '^nimma/(.*)': '<rootDir>../../node_modules/nimma/dist/cjs/$1',
-    '^@asyncapi/nunjucks-filters$': path.resolve(__dirname, '../nunjucks-filters'),
-  },
 };

package/lib/__mocks__/utils.js

@@ -13,9 +13,6 @@ utils.fetchSpec = jest.fn(async (fileUrl) => {
 utils.__isFileSystemPathValue = false;
 utils.isFileSystemPath = jest.fn(() => utils.__isFileSystemPathValue);
 
-utils.__isLocalTemplateValue = false;
-utils.isLocalTemplate = jest.fn(async () => utils.__isLocalTemplateValue);
-
 utils.__generatorVersion = '';
 utils.getGeneratorVersion = jest.fn(() => utils.__generatorVersion);
 

package/lib/generator.js

@@ -12,7 +12,6 @@ const npmPath = requireg.resolve('npm').replace('index.js','');
 const { isAsyncAPIDocument } = require('@asyncapi/parser/cjs/document');
 
 const { configureReact, renderReact, saveRenderedReactContent } = require('./renderer/react');
-const { configureNunjucks, renderNunjucks } = require('./renderer/nunjucks');
 const { validateTemplateConfig } = require('./templates/config/validator');
 const { loadTemplateConfig } = require('./templates/config/loader');
 const { isGenerationConditionMet } = require('./conditionalGeneration');
@@ -26,17 +25,14 @@ const {
   copyFile,
   exists,
   fetchSpec,
-  isReactTemplate,
   isJsFile,
   getTemplateDetails,
   convertCollectionToObject,
 } = require('./utils');
 const { parse, usesNewAPI, getProperApiDocument } = require('./parser');
-const { registerFilters } = require('./filtersRegistry');
 const { registerHooks } = require('./hooksRegistry');
 const { definitions, flatten, shorthands } = require('@npmcli/config/lib/definitions');
 
-const FILTERS_DIRNAME = 'filters';
 const HOOKS_DIRNAME = 'hooks';
 const PACKAGE_JSON_FILENAME = 'package.json';
 const GIT_IGNORE_FILENAME = '{.gitignore}';
@@ -325,9 +321,6 @@ class Generator {
     await this.parseInput(this.asyncapi, parseOptions);
     validateTemplateConfig(this.templateConfig, this.templateParams, this.asyncapi);
     await this.configureTemplate();
-    if (!isReactTemplate(this.templateConfig)) {
-      await registerFilters(this.nunjucks, this.templateConfig, this.templateDir, FILTERS_DIRNAME);
-    }
     await registerHooks(this.hooks, this.templateConfig, this.templateDir, HOOKS_DIRNAME);
     await this.launchHook('generate:before');
   }
@@ -407,10 +400,8 @@ class Generator {
    * Configure the templates based the desired renderer.
    */
   async configureTemplate() {
-    if (isReactTemplate(this.templateConfig) && this.compile) {
+    if (this.compile) {
       await configureReact(this.templateDir, this.templateContentDir, TRANSPILED_TEMPLATE_LOCATION);
-    } else {
-      this.nunjucks = configureNunjucks(this.debug, this.templateDir);
     }
   }
 
@@ -876,11 +867,8 @@ class Generator {
     const renderContent = await this.renderFile(asyncapiDocument, templateFilePath, extraTemplateData);
     if (renderContent === undefined) {
       return;
-    } else if (isReactTemplate(this.templateConfig)) {
-      await saveRenderedReactContent(renderContent, outputpath, this.noOverwriteGlobs);
-    } else {
-      await writeFile(outputpath, renderContent);
     }
+    await saveRenderedReactContent(renderContent, outputpath, this.noOverwriteGlobs);
   }
   
   /**
@@ -981,11 +969,7 @@ class Generator {
    * @return {Promise<string|TemplateRenderResult|Array<TemplateRenderResult>|undefined>}
    */
   async renderFile(asyncapiDocument, filePath, extraTemplateData = {}) {
-    if (isReactTemplate(this.templateConfig)) {
-      return await renderReact(asyncapiDocument, filePath, extraTemplateData, this.templateDir, this.templateContentDir, TRANSPILED_TEMPLATE_LOCATION, this.templateParams, this.debug, this.originalAsyncAPI);
-    }
-    const templateString = await readFile(filePath, 'utf8');
-    return renderNunjucks(asyncapiDocument, templateString, filePath, extraTemplateData, this.templateParams, this.originalAsyncAPI, this.nunjucks);
+    return await renderReact(asyncapiDocument, filePath, extraTemplateData, this.templateDir, this.templateContentDir, TRANSPILED_TEMPLATE_LOCATION, this.templateParams, this.debug, this.originalAsyncAPI);
   }
 
   /**
@@ -999,7 +983,7 @@ class Generator {
     const nonRenderableFiles = this.templateConfig.nonRenderableFiles || [];
     return Array.isArray(nonRenderableFiles) &&
     (nonRenderableFiles.some(globExp => minimatch(fileName, globExp)) ||
-    (isReactTemplate(this.templateConfig) && !isJsFile(fileName)));
+    !isJsFile(fileName));
   }
 
   /**

package/lib/templates/bakedInTemplates/core-template-client-kafka-java-quarkus/.ageneratorrc

@@ -1,6 +1,4 @@
-renderer: react
 apiVersion: v3
-generator: '>=1.3.0 <3.0.0'
 parameters:
   server:
     description: The name of the server described in AsyncAPI document
@@ -13,11 +11,11 @@ parameters:
     description: The custom name for the generated client class
     required: false
   env:
-    description: 'The environment for the generated client, e.g., dev, prod'
+    description: The environment for the generated client, e.g., dev, prod
     required: false
     default: dev
   version:
-    description: 'The version for the generated client, e.g., V1, V2'
+    description: The version for the generated client, e.g., V1, V2
     required: false
     default: V1
 nonRenderableFiles:

package/lib/templates/bakedInTemplates/core-template-client-kafka-java-quarkus/__transpiled/jest.config.js

@@ -0,0 +1,13 @@
+'use strict';
+
+require('source-map-support/register');
+
+const baseConfig = require('../../../../../../jest.config.base');
+module.exports = {
+  ...baseConfig(__dirname),
+  moduleFileExtensions: ['js', 'json', 'jsx'],
+  transform: {
+    '^.+\\.jsx?$': 'babel-jest'
+  }
+};
+//# sourceMappingURL=jest.config.js.map

package/lib/templates/bakedInTemplates/core-template-client-kafka-java-quarkus/__transpiled/jest.config.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"jest.config.js","sources":["../../../../../../../packages/templates/clients/kafka/java/quarkus/jest.config.js"],"sourcesContent":["const baseConfig = require('../../../../../../jest.config.base');\n\nmodule.exports = {\n  ...baseConfig(__dirname),\n  moduleFileExtensions: [\n    'js',\n    'json',\n    'jsx'\n  ],\n  transform: {\n    '^.+\\\\.jsx?$': 'babel-jest'\n  },\n};\n\n"],"names":["baseConfig","require","module","exports","__dirname","moduleFileExtensions","transform"],"mappings":";;;;AAAA,MAAMA,UAAU,GAAGC,OAAO,CAAC,oCAAoC,CAAC,CAAA;AAEhEC,MAAM,CAACC,OAAO,GAAG;EACf,GAAGH,UAAU,CAACI,SAAS,CAAC;AACxBC,EAAAA,oBAAoB,EAAE,CACpB,IAAI,EACJ,MAAM,EACN,KAAK,CACN;AACDC,EAAAA,SAAS,EAAE;AACT,IAAA,aAAa,EAAE,YAAA;AACjB,GAAA;AACF,CAAC;;"}

package/lib/templates/bakedInTemplates/core-template-client-kafka-java-quarkus/jest.config.js

@@ -0,0 +1,14 @@
+const baseConfig = require('../../../../../../jest.config.base');
+
+module.exports = {
+  ...baseConfig(__dirname),
+  moduleFileExtensions: [
+    'js',
+    'json',
+    'jsx'
+  ],
+  transform: {
+    '^.+\\.jsx?$': 'babel-jest'
+  },
+};
+