feat: finish migrating to react renderer

[ibishal]

Description

Updated this template to use react renderer

Related issue(s) #294

[ibishal]

Can you review this PR,

then make it support asyncapi v3 - so 2 separate PR

so that i can proceed with this

cc @derberg

[ibishal]

The package-lock.json is now included in the PR, and the test are working fine locally, can you rerun the test in this PR

cc @derberg

[sonarqubecloud[bot]]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[ibishal]

done the reviewed changes @derberg

[ibishal]

pinging you again cc @derberg

[ibishal]

nice! did you try to use the template using https://github.com/asyncapi/nodejs-ws-template?tab=readme-ov-file#how-to-use-the-template instruction? I mean the react version?

when running ag command you need to reference local copy of react based template instead of @asyncapi/nodejs-ws-template

ig i have done that, as far as i remember

[ibishal]

Lets push this by this weekend, its been pending for a long time

cc @derberg

[github-actions[bot]]

This pull request has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation.

There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

[ibishal]

cc @derberg

[derberg]

@ibishal let's better focus on moving functionality to generator directly and archiving this repo