Studio fell in production

[aeworxet]

Describe the bug

Studio is not functional at https://studio.asyncapi.com with error in console.

How to Reproduce

Open https://studio.asyncapi.com.

Expected behavior

Studio is expected to work.

[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.

[aeworxet]

The bug is caused by code from https://github.com/asyncapi/converter-js introduced in

92cfd9a0877ca2f9483d8bca0b67d8f0479aca0e

A fast solution would be to revert and then figure out what happened.

@jonaslagoni @ItshMoh

[aeworxet]

Take into account #1094 (comment), just in case.

[aeworxet]

Another fast solution would be to temporarily hard-lock the @asyncapi/converter version in both package.jsons:

./apps/studio/package.json
./apps/studio-next/package.json

"@asyncapi/converter": "1.5.0",

Choose which one is to your liking.

[jonaslagoni]

Because the converter never had a requirement that the code must be able to run in the browser, I dont think the converter will get a rollback, unless majority wants it.

Studio needs to run the conversion logic in the backend and send it to the frontend, it's a problem because a dependency is no longer browser-compatible.

[aeworxet]

Then, to get the Studio up and running right now, the only thing that is possible is to hard-lock the @asyncapi/converter on version 1.5.0 and after that start looking for a permanent solution.

[Amzani]

We can go with this option @aeworxet