[BUG] Updating Project Dependencies for Performance, Security, and Compatibility

[Ervishalpathak7]

Describe the bug.

The project dependencies need to be updated to ensure stability, security, and performance improvements. This issue aims to update all packages to their latest versions, test for compatibility, and resolve any issues that arise during the update process.

• Outdated Packages: Certain dependencies might be lagging behind their latest versions, potentially missing critical optimizations and security patches.
• Potential Vulnerabilities: Old versions of libraries may have unpatched security vulnerabilities.
• Performance Limitations: Newer package versions might offer better performance or reduced memory usage.
• Compatibility Concerns: Keeping dependencies updated ensures the CLI works well with evolving ecosystems and avoids deprecated features.

Expected behavior

• Dependencies updated to the latest stable versions.
• All existing functionality remains intact and passes tests.

Screenshots

How to Reproduce

1. Audit Existing Dependencies:

• Use npm outdated to list packages that need updates.
• Categorize updates as minor, patch, or major (breaking changes).

2. Incremental Updates:

• Update minor/patch versions first, as they are less likely to break existing functionality.
• Handle major version updates carefully by checking changelogs and adjusting code if necessary.

3. Testing & Validation:

• Run all existing test cases with npm test.
• Manually test core commands like generate, validate, and others to ensure CLI stability.
• Conduct stress tests to check for performance improvements or regressions.

4. Raise Pull Request:

• Update package.json and package-lock.json.
• Document which packages were updated and the changes introduced.
• Add notes about any breaking changes handled or improvements observed.

🥦 Browser

Brave

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

Yes I am willing to submit a PR!

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[Someshog]

Hi @Ervishalpathak7 @AayushSaini101
I've encountered the same issue while working with AsyncAPI CLI and would like to contribute to resolving it.
If there's anything I can help, please let me know. Thanks!