Hammerhead produces invalid code when dealing with destructuring and class syntax in the same line

[tobiaswaltl]

What is your Scenario?

I would like to use testcafe to test my application that contains ES6 syntax. As we need multi window support, using native automation is not an option for us.

What is the Current behavior?

Hammerhead removes the brackets after extends in the following code example and thus, creates invalid syntax: var {hasOwnProperty: gt} = x , ft = e=>class t extends (e || We) { } ;

It seems that this does only happen, when the destructuring statement is there.

What is the Expected behavior?

Hammerhead does not create invalid syntax when processing the code example above.

What is your public website URL? (or attach your complete example)

I don't have a public example, but in the repro section I have added a link to my fork with an additional unit test that demonstrates the problem.

What is your TestCafe test code?

n/a

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

1. Run the test I have created. It demonstrates how the above code example is transpiled into invalid code.

TestCafe version

3.4.0

Node.js version

18.18.2

Command-line arguments

n/a

Browser name(s) and version(s)

No response

Platform(s) and version(s)

No response

Other

No response

[github-actions[bot]]

We appreciate you taking the time to share information about this issue. We reproduced the bug and added this ticket to our internal task queue. We'll update this thread once we have news.

[Bayheck]

Hello,

As we need multi window support, using native automation is not an option for us.

Try using TestCafe v3.5.0's ‘--experimental-multiple-windows’ mode in Native Automation. Let us know if you need further assistance.

[github-actions[bot]]

This issue was automatically closed because there was no response to our request for more information from the original author. Currently, we don't have enough information to take action. Please reach out to us if you find the necessary information and are able to share it. We are also eager to know if you resolved the issue on your own and can share your findings with everyone.