feat: introduce the turborepo to the parser.js

[ayushnau]

Changes Added.

Turborepo Added.
Converted the parser repo to app, inside the turborepo.
Added the required scripts of the turborepo to the root package.json file.

Related issue(s)

Related to: #963

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide 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.

[ayushnau]

Deliverables:

1. Integrate turborepo in parser.js
2. Integrate multiparser in the parser.js.

[ayushnau]

@smoya please review the pr.

[smoya]

/dnm

[smoya]

Blocking the merge until we review it

[smoya]

We need a proper README. This is just a placeholder.

[AyushNautiyalDeveloper]

added the readme.

[smoya]

This file should go in the root of the repository

[AyushNautiyalDeveloper]

added in root.

[smoya]

You didn't move it but duplicated

[ayushnau]

@smoya It is working fine now. I changed the version and now it is working.

[smoya]

LGTM! 🚀🌔

[smoya]

@ayushnau There is an error, seems a not updated .lock file or similar https://github.com/asyncapi/parser-js/actions/runs/9291475481/job/25618079508?pr=992

[ayushnau]

@smoya updated can you check now.

[smoya]

There is an issue with our tests in CI when running under macos. It is not the first time we find this.
We need to investigate what the issue is, but not linked to this PR.

[smoya]

We can't merge this PR until #1001 gets solved. Working on it.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[ayushnau]

@smoya please check i have updated the pr.

[smoya]

@jonaslagoni can you give your 👍 now?

[jonaslagoni]

@smoya if you are happy with it, go for it 👍 Dont see anything from my side

[smoya]

@smoya if you are happy with it, go for it 👍 Dont see anything from my side

I only have one concern. I want to merge this ASAP and release it (so we can be sure everything works as expected, including CI pipeline etc). The point is that this is a chore and atm I don't see any opened PR with a mergeable status we could merge right after this one in order to do a meaningful release.
Forcing a release for this without providing any new feature or fix is not very desirable...

Any idea or suggestion @jonaslagoni ?

[jonaslagoni]

I think it's fine regardless, do what is easiest don't think too much about it 🙂

[smoya]

I'm gonna merge this as a new minor version (feat). I prefer to fail fast than cry late.

[smoya]

/rtm

[asyncapi-bot]

🎉 This PR is included in version 3.1.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[smoya]

I'm gonna merge this as a new minor version (feat). I prefer to fail fast than cry late.

Well, failed fast 😆

[7:50:15 AM] [semantic-release] [@semantic-release/npm] › ℹ Skip publishing to npm registry as package.json's private property is true

See https://github.com/asyncapi/parser-js/actions/runs/9413515248/job/25930521532#step:9:65

@ayushnau I believe you tested this as per your previous comments (to publish to your own NPM account). Anyway, we need to fix this asap as `3.1.0 published in GH is also wrong, since it is a release of the whole repo not the individual app(s).

Btw, I removed such tags and release from GH.

[smoya]

The issue comes with semantic-release and it's lack of support for monorepo. We should move into Changesets as Studio did: https://github.com/asyncapi/studio/blob/master/doc/adr/0002-use-changesets-for-publishing-and-versioning.md

I'm reverting this PR. @ayushnau Feel free to open a new one with a version that really releases each package individually.

[asyncapi-bot]

🎉 This PR is included in version 3.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀