Overarching issue for tracking progress

[Shurtu-gal]

Currently I am able to see following issues with CLI:

1. Release pipeline is not working right now (with trusted publishing):
   • Also upload of custom assets was not working (should be fixed with the release pipeline fix) [BUG] Fix release pipeline #1892
2. Need updation of dependencies, especially those with security vulnerabilities. Ref: Depends on deprecated/vulnerable packages #1836
3. Support for other schemas and languages. Ex: Avro schemas (Need discussion): [FEATURE] Avro Validation #1813
4. Docker image as well npm package size is too large. It needs to be optimized. Ref: [FEATURE] Reduce number of dependencies and install size (v2.17 needs 1700 dependencies, takes 1.7Gb of space) #1752, [ENHANCEMENT] Docker images are take too long to build and are quite large. #1798
5. Intermittent issues in Windows. Ref: [BUG] CLI Window's executable installer fails to install #1744, [BUG] Generator error when using pnpm to create documentation #1781, [BUG] Installing the CLI through Chocolatey produces bugs in generate commands #1743
6. Need transfer-issue workflow to work so that issues can be transferred to respective repos. It is being actioned in [BUG] Transfer Issue workflow not working. .github#344. Issues to be transferred:
   • Java & Kotlin - type mapping support in the asyncapi cli modelina#2397
   • Kotlin - jackson support in the asyncapi cli modelina#2398
   • [FEATURE] Generate Exported Constants for Properties with const Values modelina#2399
   • [BUG] 2.17.0 & 3.1.1 asyncapi bundle & optimise breaks fifo channels optimizer#291
   • [FEATURE] Possibility to pass render config to Modelina modelina#2400

[sarthakNITT]

@Shurtu-gal I looked on second issue deprecated packages #1836. Regarding #1836, the "nyc" coverage tool is the main source of the "glob@7" and inflight warnings. I propose we replace "nyc" with "c8" (uses native V8 coverage) and upgrade "rimraf" to v6. This would clear up the majority of the deprecation alerts. Is everyone okay with this approach?

[Shurtu-gal]

Yes, @sarthakNITT please create a PR for this will test it out accordingly.

[sarthakNITT]

@Shurtu-gal okay, I am on to working on it.

[Shurtu-gal]

@sarthakNITT I guess a PR is there already. You can help out though by putting forward suggestions and testing that nothing breaks with these upgrades.

I have already informed abt #1929 (comment) in the PR review.

[sarthakNITT]

@Shurtu-gal I reviewed the PR and I don’t think we need to add or replace a large number of dependencies.
Most deprecation warnings come indirectly from these four packages: rimraf, unzipper, mocha, @stoplight/spectral-cli
They pull in deprecated transitive deps (fstream, glob<9, mkdirp<1, rimraf<4, inflight).
Updating these four to their latest LTS versions should resolve those warnings automatically.

nyc is a special case, it still depends on older rimraf and glob even in its latest version. Replacing nyc with c8 would be the cleaner solution here.

The remaining deprecated packages are coming from AsyncAPI internal packages (mondelena-cli, generator) because these packages are using older versions of some packages. Those would need to be fixed upstream in their respective repos.

Overall, updating a small set of top-level deps should fix most issues without large-scale dependency changes.

Just a concern that latest versions of those 4 packages ask for node version >=20, so should i go with it or look or latest update compatible with node >=18?

[Shurtu-gal]

We are also moving to nodejs > 20. So that's not a problem. Updating unrelated dependency is also not a big problem.

Anyway it was a long time coming. Regaring c8 I have already commented on the PR.

[Shurtu-gal]

Also please comment on the PR about the inputs. That would be better.

[sarthakNITT]

@Shurtu-gal raised a pr. Please check it once.