@asyncapi/generator 2.8.4 → 3.0.0

package/Dockerfile

@@ -1,20 +0,0 @@
-FROM node:18-alpine
-
-ARG ASYNCAPI_GENERATOR_VERSION=1.10.9
-
-WORKDIR /app
-
-# Since 0.14.0 release of html-template chromium is needed for pdf generation
-ENV PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium-browser
-ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true
-
-# Since 0.30.0 release Git is supported and required as a dependency
-# Since 0.14.0 release of html-template chromium is needed for pdf generation.
-# More custom packages for specific template should not be added to this dockerfile. Instead, we should come up with some extensibility solution.
-# Installing latest released npm package
-RUN apk --update add git chromium && \
-    rm /var/cache/apk/* && \
-    npm install --ignore-scripts -g "@asyncapi/generator@${ASYNCAPI_GENERATOR_VERSION}"
-
-
-ENTRYPOINT [ "ag" ]

package/cli.js

@@ -1,205 +0,0 @@
-#!/usr/bin/env node
-
-const path = require('path');
-const os = require('os');
-const program = require('commander');
-const xfs = require('fs.extra');
-const { DiagnosticSeverity } = require('@asyncapi/parser/cjs');
-const packageInfo = require('./package.json');
-const Generator = require('./lib/generator');
-const Watcher = require('./lib/watcher');
-const { isLocalTemplate, isFilePath } = require('./lib/utils');
-
-const red = text => `\x1b[31m${text}\x1b[0m`;
-const magenta = text => `\x1b[35m${text}\x1b[0m`;
-const yellow = text => `\x1b[33m${text}\x1b[0m`;
-const green = text => `\x1b[32m${text}\x1b[0m`;
-
-let asyncapiDocPath;
-let template;
-const params = {};
-const noOverwriteGlobs = [];
-const disabledHooks = {};
-const mapBaseUrlToFolder = {};
-
-const parseOutput = dir => path.resolve(dir);
-
-const paramParser = v => {
-  if (!v.includes('=')) throw new Error(`Invalid param ${v}. It must be in the format of --param name=value.`);
-  const [paramName, paramValue] = v.split(/=(.+)/, 2);
-  params[paramName] = paramValue;
-  return v;
-};
-
-const noOverwriteParser = v => noOverwriteGlobs.push(v);
-
-const disableHooksParser = v => {
-  const [hookType, hookNames] = v.split(/=/);
-  if (!hookType) throw new Error('Invalid --disable-hook flag. It must be in the format of: --disable-hook <hookType> or --disable-hook <hookType>=<hookName1>,<hookName2>,...');
-  if (hookNames) {
-    disabledHooks[hookType] = hookNames.split(/,/);
-  } else {
-    disabledHooks[hookType] = true;
-  }
-};
-
-const mapBaseUrlParser = v => {
-  // Example value for regular expression: https://schema.example.com/crm/:./test/docs/
-  // it splits on last occurrence of : into the groups all, url and folder
-  const re = /(.*):(.*)/g;
-  let mapping = [];
-  if ((mapping = re.exec(v))===null || mapping.length!==3) {
-    throw new Error('Invalid --map-base-url flag. A mapping <url>:<folder> with delimiter : expected.');
-  }
-
-  // Folder is without trailing slash, so make sure that url has also no trailing slash:
-  mapBaseUrlToFolder.url = mapping[1].replace(/\/$/, '');
-  mapBaseUrlToFolder.folder = path.resolve(mapping[2]);
-
-  const isURL = /^https?:/;
-  if (!isURL.test(mapBaseUrlToFolder.url.toLowerCase())) {
-    throw new Error('Invalid --map-base-url flag. The mapping <url>:<folder> requires a valid http/https url and valid folder with delimiter `:`.');
-  }
-};
-
-const showError = err => {
-  console.error(red('Something went wrong:'));
-  console.error(red(err.stack || err.message));
-  if (err.diagnostics) {
-    const errorDiagnostics = err.diagnostics.filter(diagnostic => diagnostic.severity === DiagnosticSeverity.Error);
-    console.error(red(`Errors:\n${JSON.stringify(errorDiagnostics, undefined, 2)}`));
-  }
-};
-const showErrorAndExit = err => {
-  showError(err);
-  process.exit(1);
-};
-
-program
-  .version(packageInfo.version)
-  .arguments('<asyncapi> <template>')
-  .action((fileLoc, tmpl) => {
-    asyncapiDocPath = fileLoc;
-    template = tmpl;
-  })
-  .option('-d, --disable-hook [hooks...]', 'disable a specific hook type or hooks from given hook type', disableHooksParser)
-  .option('--debug', 'enable more specific errors in the console')
-  .option('-i, --install', 'installs the template and its dependencies (defaults to false)')
-  .option('-n, --no-overwrite <glob>', 'glob or path of the file(s) to skip when regenerating', noOverwriteParser)
-  .option('-o, --output <outputDir>', 'directory where to put the generated files (defaults to current directory)', parseOutput, process.cwd())
-  .option('-p, --param <name=value>', 'additional param to pass to templates', paramParser)
-  .option('--force-write', 'force writing of the generated files to given directory even if it is a git repo with unstaged files or not empty dir (defaults to false)')
-  .option('--disable-warning', 'disable "ag" deprecation warning (defaults to false)')
-  .option('--watch-template', 'watches the template directory and the AsyncAPI document, and re-generate the files when changes occur. Ignores the output directory. This flag should be used only for template development.')
-  .option('--map-base-url <url:folder>','maps all schema references from base url to local folder',mapBaseUrlParser)
-  .parse(process.argv);
-
-if (!program.disableWarning) {
-  console.warn(yellow(
-    'Warning: The "ag" CLI is deprecated and will be removed in a future release. Please use the AsyncAPI CLI instead. See release notes for details: https://github.com/asyncapi/generator/releases/tag/%40asyncapi%2Fgenerator%402.6.0. You can hide this working using --disable-warning flag.')
-  );
-}
-
-if (!asyncapiDocPath) {
-  console.error(red('> Path or URL to AsyncAPI file not provided.'));
-  program.help(); // This exits the process
-}
-const isAsyncapiDocLocal = isFilePath(asyncapiDocPath);
-
-xfs.mkdirp(program.output, async err => {
-  if (err) return showErrorAndExit(err);
-  try {
-    await generate(program.output);
-  } catch (e) {
-    return showErrorAndExit(e);
-  }
-
-  // If we want to watch for changes do that
-  if (program.watchTemplate) {
-    let watcher;
-    const watchDir = path.resolve(template);
-    const outputPath = path.resolve(watchDir, program.output);
-    const transpiledTemplatePath = path.resolve(watchDir, Generator.TRANSPILED_TEMPLATE_LOCATION);
-    const ignorePaths = [outputPath, transpiledTemplatePath];
-    // Template name is needed as it is not always a part of the cli commad
-    // There is a use case that you run generator from a root of the template with `./` path
-    const templateName = require(path.resolve(watchDir,'package.json')).name;
-
-    if (isAsyncapiDocLocal) {
-      console.log(`[WATCHER] Watching for changes in the template directory ${magenta(watchDir)} and in the AsyncAPI file ${magenta(asyncapiDocPath)}`);
-      watcher = new Watcher([asyncapiDocPath, watchDir], ignorePaths);
-    } else {
-      console.log(`[WATCHER] Watching for changes in the template directory ${magenta(watchDir)}`);
-      watcher = new Watcher(watchDir, ignorePaths);
-    }
-    // Must check template in its installation path in generator to use isLocalTemplate function
-    if (!await isLocalTemplate(path.resolve(Generator.DEFAULT_TEMPLATES_DIR, templateName))) {
-      console.warn(`WARNING: ${template} is a remote template. Changes may be lost on subsequent installations.`);
-    }
-
-    await watcher.watch(watcherHandler, (paths) => {
-      showErrorAndExit({ message: `[WATCHER] Could not find the file path ${paths}, are you sure it still exists? If it has been deleted or moved please rerun the generator.` });
-    });
-  }
-});
-
-/**
- * Generates the files based on the template.
- * @param {*} targetDir The path to the target directory.
- */
-function generate(targetDir) {
-  return new Promise(async (resolve, reject) => {
-    try {
-      const generator = new Generator(template, targetDir || path.resolve(os.tmpdir(), 'asyncapi-generator'), {
-        templateParams: params,
-        noOverwriteGlobs,
-        disabledHooks,
-        forceWrite: program.forceWrite,
-        install: program.install,
-        debug: program.debug,
-        mapBaseUrlToFolder
-      });
-
-      if (isAsyncapiDocLocal) {
-        await generator.generateFromFile(path.resolve(asyncapiDocPath));
-      } else {
-        await generator.generateFromURL(asyncapiDocPath);
-      }
-      console.log(green('\n\nDone! ✨'));
-      console.log(`${yellow('Check out your shiny new generated files at ') + magenta(program.output) + yellow('.')}\n`);
-      resolve();
-    } catch (e) {
-      reject(e);
-    }
-  });
-}
-
-async function watcherHandler(changedFiles) {
-  console.clear();
-  console.log('[WATCHER] Change detected');
-  for (const [, value] of Object.entries(changedFiles)) {
-    let eventText;
-    switch (value.eventType) {
-    case 'changed':
-      eventText = green(value.eventType);
-      break;
-    case 'removed':
-      eventText = red(value.eventType);
-      break;
-    case 'renamed':
-      eventText = yellow(value.eventType);
-      break;
-    default:
-      eventText = yellow(value.eventType);
-    }
-    console.log(`\t${magenta(value.path)} was ${eventText}`);
-  }
-  console.log('Generating files');
-  try {
-    await generate(program.output);
-  } catch (e) {
-    showError(e);
-  }
-}
-
-process.on('unhandledRejection', showErrorAndExit);

package/docs/migration-cli.md

@@ -1,70 +0,0 @@
----
-title: "Migrating from `ag` CLI to AsyncAPI CLI"
-weight: 260
----
-
-This guide provides detailed instructions on how to transition from the old `ag` Generator CLI  to the new AsyncAPI CLI.
-
-## Options Overview
-
-Here is a list of `ag` options and their equivalents in the AsyncAPI CLI:
-
-- **-d, --disable-hook [hooks...]**
-  - **AsyncAPI CLI equivalent:** `asyncapi generate fromTemplate <ASYNCAPI> <TEMPLATE> --disable-hook <hookType>=<hookName>`
-
-- **--debug**
-  - **AsyncAPI CLI equivalent:** `asyncapi generate fromTemplate <ASYNCAPI> <TEMPLATE> --debug`
-
-- **-i, --install**
-  - **AsyncAPI CLI equivalent:** `asyncapi generate fromTemplate <ASYNCAPI> <TEMPLATE> --install`
-
-- **-n, --no-overwrite &#x3C;glob&#x3E;**
-  - **AsyncAPI CLI equivalent:** `asyncapi generate fromTemplate <ASYNCAPI> <TEMPLATE> --no-overwrite <glob>`
-
-- **-o, --output &#x3C;outputDir&#x3E;**
-  - **AsyncAPI CLI equivalent:** `asyncapi generate fromTemplate <ASYNCAPI> <TEMPLATE> --output <outputDir>`
-
-- **-p, --param &#x3C;name&#x3D;value&#x3E;**
-  - **AsyncAPI CLI equivalent:** `asyncapi generate fromTemplate <ASYNCAPI> <TEMPLATE> --param <name=value>`
-
-- **--force-write**
-  - **AsyncAPI CLI equivalent:** `asyncapi generate fromTemplate <ASYNCAPI> <TEMPLATE> --force-write`
-
-- **--watch-template**
-  - **AsyncAPI CLI equivalent:** `asyncapi generate fromTemplate <ASYNCAPI> <TEMPLATE> --watch`
-
-- **--map-base-url &#x3C;url:folder&#x3E;**
-  - **AsyncAPI CLI equivalent:** `asyncapi generate fromTemplate <ASYNCAPI> <TEMPLATE> --map-base-url <url:folder>`
-
-## Migration Steps
-
-### 1. Install AsyncAPI CLI
-
-There are multiple different artifacts that AsyncAPI CLI is provided as. Get familiar with the [official CLI installation guide](https://www.asyncapi.com/docs/tools/cli/installation).
-
-### 2. Update Your Commands
-
-Replace the deprecated `ag` commands with the AsyncAPI CLI equivalents. Below are examples of how to update your commands:
-
-**Using `ag`**:
-```
-ag ./asyncapi.yaml ./template -o ./output -p param1=value1 --debug --install --disable-hook hookType=hookName
-```
-
-**Using AsyncAPI CLI**:
-```
-asyncapi generate fromTemplate ./asyncapi.yaml ./template -o ./output -p param1=value1 --debug --install --disable-hook hookType=hookName
-```
-
-Notice that the change basically related to changing from `ag` to `asyncapi generate fromTemplate`.
-
-### 3. Verify and Test
-
-Run the updated commands to ensure they work as expected and verify that the output files are generated correctly.
-
-## Additional Resources
-
-**CLI Documentation**: [AsyncAPI CLI Documentation](https://www.asyncapi.com/docs/tools/cli)
-**Installation**: [AsyncAPI CLI Installation](https://www.asyncapi.com/docs/tools/cli/installation)
-**Usage**: [AsyncAPI CLI Usage](https://www.asyncapi.com/docs/tools/cli/usage)
-**Support**: For any issues with CLI, create an issue in [CLI repository](https://github.com/asyncapi/cli).

package/docs/migration-nunjucks-react.md

@@ -1,144 +0,0 @@
----
-title: "Migrating from Nunjucks to React render engine"
-weight: 250
----
-
-The AsyncAPI Generator is moving away from Nunjucks templates in favor of React templates. This guide will help you migrate your existing Nunjucks templates to React. For a comprehensive understanding of why we introduced React as an alternative in 2021 and why we're now removing Nunjucks entirely, please read our article [React as a Generator Engine](https://www.asyncapi.com/blog/react-as-generator-engine). The principles discussed in this article still apply to our current transition.
-
-## Step-by-step migration guide
-
-### 1. Update package.json
-
-Change your template configuration in `package.json`:
-
-```json
-{
-"generator": {
-"renderer": "react"
-}
-}
-```
-
-Once the deprecation period has ended, and we remove the default Nunjucks, the React render engine will be used by default and this setting will no longer be needed to configure
-
-### 2. Install dependencies
-
-Install the necessary React dependencies:
-
-```bash
-npm install @asyncapi/generator-react-sdk
-```
-
-### 3. File naming
-
-In Nunjucks, the template's filename directly corresponds to the output file. For example, a template named **index.html** will generate an **index.html** file.
-
-In React, the filename of the generated file is not controlled by the file itself, but rather by the `File` component. The React component itself can be named anything with a `.js` extension because the output filename is controlled by the `name` attribute of the `File` component used inside the template file. Below you can see some examples of filenames: 
-
-Nunjucks: `index.html`
-React: `index.js` or `index.html.js` or `anything-you-want.js`
-
-### 4. Basic template structure
-
-Nunjucks:
-```js
-<h1>{{ asyncapi.info().title() }}</h1>
-<p>{{ asyncapi.info().description() }}</p>
-```
-
-React:
-```js
-import { File } from '@asyncapi/generator-react-sdk';
-
-export default function({ asyncapi }) {
-  return (
-    <File name="index.html">
-      <h1>{asyncapi.info().title()}</h1>
-      <p>{asyncapi.info().description()}</p>
-    </File>
-  );
-}
-```
-
-### 5. Macros and Partials
-
-Replace macros with React components:
-
-Nunjucks:
-```js
-{% macro renderChannel(channel) %}
-  <div class="channel">
-    <h3>{{ channel.address() }}</h3>
-    <p>{{ channel.description() }}</p>
-  </div>
-{% endmacro %}
-
-{{ renderChannel(someChannel) }}
-```
-
-React:
-```js
-// components/Channel.js
-import { Text } from '@asyncapi/generator-react-sdk';
-
-export function Channel({ channel }) {
-  return (
-    <Text>
-      <div className="channel">
-        <h3>{channel.address()}</h3>
-        <p>{channel.description()}</p>
-      </div>
-    </Text>
-  );
-}
-
-// Main template
-import { File, Text } from '@asyncapi/generator-react-sdk';
-import { Channel } from './components/Channel';
-
-export default function({ asyncapi }) {
-  return (
-    <File name="channels.html">
-      <Text>
-        <h2>Channels</h2>
-      </Text>
-      {asyncapi.channels().map(channel => (
-        <Channel channel={channel} />
-      ))}
-    </File>
-  );
-}
-```
-
-### 6. File template 
-
-Check the [detailed guide on file templates](file-templates) to learn what is the difference between templating multiple file outputs in Nunjucks and React.
-
-### 7. Models generation
-
-If you have a template written with Nunjucks, it is almost certain that you have your own custom models, classes, or types templates in place. Instead of migrating them to React render engine we strongly advise you to delegate models generation to AsyncAPI Modelina project. Learn more about [how to add models generation using Modelina](https://www.asyncapi.com/docs/tools/generator/model-generation).
-
-## Additional Resources and Information
-
-### Template Examples
-For a complete example of React features in use, please refer to the [AsyncAPI Template for Generator Templates](https://github.com/asyncapi/template-for-generator-templates). The `master` branch demonstrates all React features, while the `nunjucks` branch shows the old Nunjucks implementation. This comparison can be particularly helpful in understanding the differences and migration process.
-
-### Filters to Helpers
-If you've been using Nunjucks filters placed in the `filters` directory, you can still use this functionality in React. However, they should be treated as normal functions that you import into your components. We recommend renaming the `filters` directory to `helpers` to better reflect their new usage in React.
-
-### Hooks Remain Unchanged
-It's important to note that hooks remain unchanged in this migration process. Hooks are not related to the render engine functionality, so you can continue to use them as you have been.
-
-### Testing your migration
-
-After migrating, test your template thoroughly:
-
-1. Run the generator using your new React template
-2. Compare the output with the previous Nunjucks template output
-3. Check for any missing or incorrectly rendered content
-
-Consider implementing snapshot tests for your template before starting the migration. This will ease the review of changes in comparing the content rendered after render engine changes. Snapshot tests allow you to have tests that will persist expected output from Nunjucks template, and compare it with output generated after the migration. Check out an [example of such snapshot integration test for our internal react template we use for development and testing](https://github.com/asyncapi/generator/blob/master/apps/generator/test/integration.test.js#L66).
-
-## Conclusion
-
-Migrating from Nunjucks to React templates may require some initial effort, but it will result in more maintainable code. You can learn more about why we introduced the React render engine from article [React as a Generator Engine](https://www.asyncapi.com/blog/react-as-generator-engine).

package/docs/nunjucks-render-engine.md

@@ -1,83 +0,0 @@
----
-title: "Nunjucks render engine"
-weight: 120
----
-
-> **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).
-
-[Nunjucks](https://mozilla.github.io/nunjucks) is the default render engine, however, we strongly recommend adopting the [React](#react) engine.
-
-### Common assumptions
-
-1. Templates may contain [Nunjucks filters or helper functions](https://mozilla.github.io/nunjucks/templating.html#builtin-filters). [Read more about filters](#filters).
-1. Templates may contain `partials` (reusable chunks). They must be stored in the `.partials` directory under the template directory. [Read more about partials](#partials).
-1. Templates may contain multiple files. Unless stated otherwise, all files will be rendered.
-1. The default variables you have access to in any the template file are the following:
-   - `asyncapi` that 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` that is an original spec file before it is parsed. 
-   - `params` that contain the parameters provided when generating.
-
-### Partials
-
-Files from the `.partials` directory do not end up with other generated files in the target directory. In this directory you should keep reusable templates chunks that you can [include](https://mozilla.github.io/nunjucks/templating.html#include) in your templates. You can also put there [macros](https://mozilla.github.io/nunjucks/templating.html#macro) to use them in templates, like in below example:
-
-```html
-{# tags.html #}
-{% macro tags(tagList) %}
-<div class="mt-4">
-  {% for tag in tagList %}
-    <span class="bg-grey-dark font-normal text-sm no-underline text-white rounded lowercase mr-2 px-2 py-1" title="{{tag.description()}}">{{tag.name()}}</span>
-  {% endfor %}
-</div>
-{% endmacro %}
-
-{# operations.html #}
-{% from "./tags.html" import tags %}
-{{ tags(operation.tags()) }}
-```
-
-### Filters
-
-A filter is a helper function that you can create to perform complex tasks. They are JavaScript files that register one or many [Nunjuck filters](https://mozilla.github.io/nunjucks/api.html#custom-filters). The generator parses all the files in the `filters` directory. Functions exported from these files are registered as filters.
-
-You can use the filter function in your template as in the following example:
-
-```js
-const {{ channelName | camelCase }} = '{{ channelName }}';
-```
-
-The generator also supports asynchronous filters. Asynchronous filters receive as the last argument a callback to resume rendering. Asynchronous filters must be annotated with the `async` keyword. Make sure to call the callback with two arguments: `callback(err, res)`. `err` can be `null`. See the following example of how to use asynchronous filters:
-
-```js
-const filter = module.exports;
-
-async function asyncCamelCase(str, callback) {
-  try {
-    const result = // logic for camel casing str
-    callback(null, result);
-  } catch (error) {
-    callback(error);
-  }
-}
-filter.renderAsyncContent = renderAsyncContent;
-
-// using in template
-{{ channelName | asyncCamelCase }}
-```
-
-Unfortunately, if you need to use Promise, filter still must be annotated with the `async` keyword:
-
-```js
-async function asyncCamelCase(str, callback) {
-  return new Promise((resolve, reject) => {
-    // logic with callback
-  });
-}
-```
-
-In case you have more than one template and want to reuse filters, you can put them in a single library. You can configure such a library in the template configuration under `filters` property. To learn how to add such filters to configuration, [read more about the configuration file](configuration-file).
-
-
-You can also use the official AsyncAPI [nunjucks-filters](https://github.com/asyncapi/generator/tree/master/apps/nunjucks-filters) which is included by default in the generator library.
-
-> **Note:**  The nunjucks-filters is deprecated, and you should migrate to react-renderer 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).

package/lib/filtersRegistry.js

@@ -1,134 +0,0 @@
-const path = require('path');
-const fs = require('fs');
-const xfs = require('fs.extra');
-const { isAsyncFunction, registerTypeScript } = require('./utils');
-const nunjucksFilters = require('@asyncapi/nunjucks-filters');
-
-/**
- * Registers all template filters.
- * @deprecated This method is deprecated. For more details, see the release notes: https://github.com/asyncapi/generator/releases/tag/%40asyncapi%2Fgenerator%402.6.0
- * @param {Object} nunjucks Nunjucks environment.
- * @param {Object} templateConfig Template configuration.
- * @param {String} templateDir Directory where template is located.
- * @param {String} filtersDir Directory where local filters are located.
- */
-module.exports.registerFilters = async (nunjucks, templateConfig, templateDir, filtersDir) => {
-  await registerLocalFilters(nunjucks, templateDir, filtersDir);
-  registerConfigFilters(nunjucks, templateDir, templateConfig);
-
-  // Register Nunjucks filters from the 'nunjucks-filters' module without needing to list them in package.json or .ageneratorrc file.
-  addFilters(nunjucks, nunjucksFilters);
-};
-
-/**
- * Registers the local template filters.
- * @deprecated This method is deprecated. For more details, see the release notes: https://github.com/asyncapi/generator/releases/tag/%40asyncapi%2Fgenerator%402.6.0
- * @private
- * @param {Object} nunjucks Nunjucks environment.
- * @param {String} templateDir Directory where template is located.
- * @param {String} filtersDir Directory where local filters are located.
- */
-function registerLocalFilters(nunjucks, templateDir, filtersDir) {
-  return new Promise((resolve, reject) => {
-    const localFilters = path.resolve(templateDir, filtersDir);
-
-    if (!fs.existsSync(localFilters)) return resolve();
-
-    const walker = xfs.walk(localFilters, {
-      followLinks: false
-    });
-
-    walker.on('file', async (root, stats, next) => {
-      try {
-        const filePath = path.resolve(
-          templateDir,
-          path.resolve(root, stats.name)
-        );
-
-        registerTypeScript(filePath);
-        // If it's a module constructor, inject dependencies to ensure consistent usage in remote templates in other projects or plain directories.
-        delete require.cache[require.resolve(filePath)];
-        const mod = require(filePath);
-
-        addFilters(nunjucks, mod);
-
-        next();
-      } catch (e) {
-        reject(e);
-      }
-    });
-
-    walker.on('errors', (root, nodeStatsArray) => {
-      reject(nodeStatsArray);
-    });
-
-    walker.on('end', async () => {
-      resolve();
-    });
-  });
-}
-
-/**
- * Registers the additionally configured filters.
- * @deprecated This method is deprecated. For more details, see the release notes: https://github.com/asyncapi/generator/releases/tag/%40asyncapi%2Fgenerator%402.6.0
- * @private
- * @param {Object} nunjucks Nunjucks environment.
- * @param {String} templateDir Directory where template is located.
- * @param {Object} templateConfig Template configuration.
- */
-async function registerConfigFilters(nunjucks, templateDir, templateConfig) {
-  const confFilters = templateConfig.filters;
-  const DEFAULT_MODULES_DIR = 'node_modules';
-  if (!Array.isArray(confFilters)) return;
-
-  const promises = confFilters.map(async filtersModule => {
-    let mod;
-    let filterName = filtersModule;
-    try {
-      //first we try to grab module with filters by the module name
-      //this is when generation is used on production using remote templates
-      mod = require(filterName);
-    } catch (error) {
-      //in case template is local but was not installed in node_modules of the generator then we need to explicitly provide modules location
-      try {
-        filterName = path.resolve(templateDir, DEFAULT_MODULES_DIR, filtersModule);
-        mod = require(filterName);
-      } catch (e) {
-        //sometimes it may happen that template is located in node_modules with other templates and its filter package is on the same level as template, as it is shared with other templates
-        try {
-          filterName = path.resolve(templateDir, '../..', filtersModule);
-          mod = require(filterName);
-        } catch (error) {
-          //in rare cases, especially in isolated tests, it may happen that installation
-          //ends but is not yet fully completed, so initial require of the same path do not work
-          //but in next attempt it works
-          //we need to keep this workaround until we find a solution
-          mod = require(filterName);
-        }
-      }
-    }
-    return addFilters(nunjucks, mod);
-  });
-
-  await Promise.all(promises);
-}
-
-/**
- * Add filter functions to Nunjucks environment. Only owned functions from the module are added.
- * @deprecated This method is deprecated. For more details, see the release notes: https://github.com/asyncapi/generator/releases/tag/%40asyncapi%2Fgenerator%402.6.0
- * @private
- * @param {Object} nunjucks Nunjucks environment.
- * @param {Object} filters Module with functions.
- */
-function addFilters(nunjucks, filters) {
-  Object.getOwnPropertyNames(filters).forEach((key) => {
-    const value = filters[key];
-    if (!(value instanceof Function)) return;
-
-    if (isAsyncFunction(value)) {
-      nunjucks.addFilter(key, value, true);
-    } else {
-      nunjucks.addFilter(key, value);
-    }
-  });
-}