[BUG] deoptimisation warning

[lightning-sagar]

Describe the bug

Generator: latest
Template: latest

[BABEL] Note: The code generator has deoptimised the styling of /Users/roman/Code/GitHub/**********/node_modules/@asyncapi/html-template/template/js/asyncapi-ui.min.js as it exceeds the max of 500KB

Expected behavior

The warning should not appear in the console, or there should be a way to disable it.

Screenshots

How to Reproduce

1. Install the latest generator and html-template.
2. Run the asyncapi generator generate command using html-template.
3. Observe the output in the console.

🖥️ Device Information (optional)

• Operating System (OS):
• Browser:
• Browser Version:

👀 Have you checked for similar open issues?

• I checked and didn't find a 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!

---

This issue was noticed in #717.

---

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

[dosubot]

The Babel deoptimization warning appears because the generator's transpilation pipeline processes all JS files in the template, including large minified files like asyncapi-ui.min.js, which triggers Babel's warning when the file exceeds 500KB. This warning is informational and does not block generation—the output is still produced successfully, but Babel skips certain styling optimizations for performance reasons [source].

Currently, there is no built-in way to suppress or turn off this warning in the generator or html-template configuration [source]. Downgrading to older versions of the generator and template can avoid the warning, but that's not recommended for long-term use [source]. A workaround mentioned in Slack is to use the --param='singleFile=true' parameter, but this does not directly suppress the Babel warning [source].

The best technical path forward is to update the generator's transpiler to skip Babel processing for large/minified files (like .min.js), or to add a configuration option (such as a compile flag) to control whether transpilation runs. This logic would need to be added to the transpiler entry point in the generator codebase, specifically where Babel is invoked via Rollup [source].

If you're interested in submitting a PR, focus on adding an exclude/ignore pattern for large/minified files in the transpiler pipeline, or implementing the planned compile option to skip unnecessary transpilation. Let me know if you want help planning the PR or need more details on the relevant code locations.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[SHUBHANSHU602]

Hey , can I take this?

[lightning-sagar]

sorry @SHUBHANSHU602 , I am working on this issue. please look for the stale issue or some other issue in the mean time.