Identifying source of notFoundError
I’m certain I’m just overlooking something obvious, but I was going mildly crazy this week when my console logs were showing “Warning: notFoundError was encountered on the route with ID “root” …
I couldn’t figure out what was causing it. Was it a missing favicon.ico being requested by the browser? Nope. Was it a tab I had open in one of many windows that was pointed to a route that no longer existed and was reloading itself for some reason? Nope. Nothing showing as 404 in Chrome dev tools either.
Anyway, eventually figured out that it was Chrome Dev Tools looking for a devtools.json file (and that request does not actually show in the dev tools network tab).
Is there a way to see what URL that is being requested/served is triggering the notFoundError vs just saying “root”?
Thanks!
6 Replies
absent-sapphire•3mo ago
is this on router or start?
dependent-tanOP•3mo ago
@Manuel Schiller My bad, it was Start, however I had made an assumption this was Router-related within Start (bad assumption)!
absent-sapphire•3mo ago
no worries
so you want better logs essentially ?
dependent-tanOP•3mo ago
It would be helpful, yes. Minimally, when a notFoundError is triggered it would be wonderful if the request URL was also included in the log output.
absent-sapphire•3mo ago
sounds useful. can you please create a GitHub issue for this so we can track it?
dependent-tanOP•3mo ago
Will do!