Uncaught Error

[andelkocvjetkovic]

Uncaught Error

[SeanCassiere]

@andelkocvjetkovic this isn't something that requires intervention from you. No further error handling is required on your-part.

Very simply, the Error is printed out to the console since the application has encountered an error (intentional or not). You can choose to customize how you display the Error to the user using the errorComponent, but nevertheless an Error has occurred. As such, the error is printed to the console.

[hugocostadev]

check this issue, maybe it's the same...

#1480

[andelkocvjetkovic]

I'm on "@tanstack/react-router": "1.28.1", so I don't think it is related

[andelkocvjetkovic]

The issue is present in "@tanstack/react-router": "1.31.1" as well

[SeanCassiere]

A couple of questions:

1. Just to be clear, the issue here is that we are logging the error to the console?
2. Why is logging the error to the console bad?

It's important to remember that this is client-sided, so there's no chance of SECRETS being revealed. Also, you'll only ever get here when there has been an error and the errorComponent has been triggered, and by default,errors are always printed to the console.

We'd need a valid reason to change this behaviour since some users have hooks that use the output of the console and that this isn't a show-stopping problem or a bug. Its currently, the intended behaviour.

[andelkocvjetkovic]

My question is why I'm getting an 'Uncaught Error' in my console. Is this something I should take care of, and how precisely should I handle this?

Thanks.