Lukasz Gornicki

@ibishal it is big. Template itself is not complex, but for sure complexity comes with fact that you need to first migrate it to use generator's react engine, and then...

no other workflows here than from `.github` repo - can be closed

**Scope of this issue** Cleanup `package.json` from the following: - remove script `"release": "semantic-release"` - remove the following `devDependencies` and then run `npm install` ``` @semantic-release/commit-analyzer @semantic-release/github @semantic-release/npm @semantic-release/release-notes-generator conventional-changelog-conventionalcommits...

@fmvilas isn't this one https://github.com/asyncapi/parser-js/issues/46 about Avro in JS Parser?

**Scope of this issue** Cleanup `package.json` from the following: - remove script `"release": "semantic-release"` - remove the following `devDependencies` and then run `npm install` ``` @semantic-release/commit-analyzer @semantic-release/github @semantic-release/npm @semantic-release/release-notes-generator conventional-changelog-conventionalcommits...

Does it really make sense in 2021?

The problem is that not everything in AsyncAPI document can be validated with AsyncAPI JSON Schema. So we need a parser. Models could be generated with https://github.com/asyncapi/modelina maybe 🤔 Most...

for the record, correct draft for any v2 version is draft 7 and not 4

v3 release done, and coincidence is that it also support asyncapi v3 https://github.com/asyncapi/nodejs-template/releases/tag/v3.0.0 anyway, if there are any issues, feel free to report them

@meteatamel thanks! opened PR to CLI -> https://github.com/asyncapi/cli/pull/1412