I think the problem is because your JS is run within the Hype JS, the error almost always refers to the hype JS, therefore you do not get a line number or clickable code reference to the real line in your code that you have the syntax error. You have to go through where you suspect it is in any recent changes you have made.
So for example. If I put an extra “.” in one of my calls in a functions,
I will get an error.
Error (index_hype_generated_script.js, line 5)
message: "Unexpected token '.'. Expected a property name after '.'."
stack: "eval@[native code]↵k@http://127.0.0.1:57652/preview/A9C2C447-C4E3-4FCF-910C-91CA75282696-53075-0002C863BDC1E0D7/index.hyperesources/index_hype_generated_script.js?81369:5:13497↵http://127.0.0.1:57652/preview/A9C2C447-C4E3-4FCF-910C-91CA75282696-53075-0002C863BDC1E0D7/index.hyperesources/HYPE-466.thin.min.js:101:368↵global code@http://127.0.0.1:57652/preview/A9C2C447-C4E3-4FCF-910C-91CA75282696-53075-0002C863BDC1E0D7/index.hyperesources/HYPE-466.thin.min.js:101:373"
Clicking on the link should take me to the line of code with the issue. But it takes me to a line in the hype_generated_script.js.
Now this is an easy one to find. in you code. While in the console and after clicking the code reference link. use command -F and search for “…” this will take you to the code with the extra “.”
It is not perfect but will show you in which function and where the problem is.
But that is an easy one. If you had an extra “}” or something missing then you have to start looking at you code bit by bit.