How to locate / debug console errors - Syntax & React related?

Hi there, I know some console errors with Squarespace are normal, but there are some extra ones that I'm pretty sure are actual issues. The trouble is, I'm not even sure how to locate these errors, much less do anything with them.

These errors are appearing across my site, which leads me to believe it may be something I'm putting in Code Injection from a 3rd party plugin. But I have no idea where they would be given the line number references here don't seem to point to anything and are different on each page. See bolded parts.

URL: https://www.youbelongsd.com/membership-page

membership-page:4895 Uncaught SyntaxError: Invalid or unexpected token

membership-page:4933 Uncaught SyntaxError: missing ) after argument list

blur.js:42 Uncaught (in promise) Error: Minified React error #321; visit https://reactjs.org/docs/error-decoder.html?invariant=321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

    at it (blur.js:42:3933)

    at s.useContext (blur.js:42:5675)

    at cr (blur.js:57:31858)

    at blur.js:61:494

    at blur.js:126:5191

    at Generator.next (<anonymous>)

    at I (blur.js:126:4967)

how it looks on the default home page:

URL: https://www.youbelongsd.com/

www.youbelongsd.com/:2833 Uncaught SyntaxError: Invalid or unexpected token 

www.youbelongsd.com/:2871 Uncaught SyntaxError: Invalid or unexpected token 

blur.js:42 Uncaught (in promise) Error: Minified React error #321; visit https://reactjs.org/docs/error-decoder.html?invariant=321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at it (blur.js:42:3933)
    at s.useContext (blur.js:42:5675)
    at cr (blur.js:57:31858)
    at blur.js:61:494
    at blur.js:126:5191
    at Generator.next (<anonymous>)
    at I (blur.js:126:4967)

I think you should discuss this issue with the third party which you are working with. They can give you a helpful suggestion

5 hours ago, Beyondspace said:

I think you should discuss this issue with the third party which you are working with. They can give you a helpful suggestion

Thank you. I have a number of plugins currently in use, so I'll have to go through and narrow down which one it may be.

On 3/3/2023 at 1:15 AM, creedon said:

It may be helpful to know that for diagnostic purposes you want to have your Inspector window open, clear the console messages, then reload the page. From there you should have full access to the errors and you can open the errors, arrow toggle, and trace down errors.

At least that is how it works in Chrome DevTools. I assume other browsers have similar diagnostic tools.

Thank you!! I did not know this, it helped me troubleshoot several of the errors myself.