DefaultGlobalNotFound in production
I hope this message finds you well.
I am currently working on a desktop application developed with React and Electron. To enhance TypeScript integration, I opted for Tanstack Router over React Router. I acknowledge that my error may pertains to this specific and somewhat unique environment, involving the Electron-Vite boilerplate (https://electron-vite.org/) for scaffolding the project.
While the routing functions flawlessly in the development environment, the challenge arises after building the project. Instead of displaying the expected routes, the application shows <p>Not Found</p>—the default global not found component discovered during my investigation of the library archives.
Given the niche nature of my problem, I seek guidance on debugging the application in a production environment. Is it possible to allow the application to crash, rather than displaying the DefaultGlobalNotFound component, which currently obscures potentially helpful error messages? I've heard about Tanstack Router dev tools—can they be employed post-build by simulating a hardcoded development environment, allowing for more effective debugging in production?
My immediate goal is to comprehend the nature of the not found error, identify potential causes, and receive more detailed error messages. It's challenging because the issue manifests in production but not in the development environment.
Your insights and assistance would be greatly appreciated.
Thank you,
I am currently working on a desktop application developed with React and Electron. To enhance TypeScript integration, I opted for Tanstack Router over React Router. I acknowledge that my error may pertains to this specific and somewhat unique environment, involving the Electron-Vite boilerplate (https://electron-vite.org/) for scaffolding the project.
While the routing functions flawlessly in the development environment, the challenge arises after building the project. Instead of displaying the expected routes, the application shows <p>Not Found</p>—the default global not found component discovered during my investigation of the library archives.
Given the niche nature of my problem, I seek guidance on debugging the application in a production environment. Is it possible to allow the application to crash, rather than displaying the DefaultGlobalNotFound component, which currently obscures potentially helpful error messages? I've heard about Tanstack Router dev tools—can they be employed post-build by simulating a hardcoded development environment, allowing for more effective debugging in production?
My immediate goal is to comprehend the nature of the not found error, identify potential causes, and receive more detailed error messages. It's challenging because the issue manifests in production but not in the development environment.
Your insights and assistance would be greatly appreciated.
Thank you,
Next generation Electron build tooling based on Vite.
