hm... yeah I was thinking about triggering the functions that the components start until I find where the error starts when the message is unconclusive

the very point of components is to be able to modularize things, you can swap out every other component to a stub, and also swap out the internal mutable parts of your component if needed, to test each in isolation

components, if used properly, make it very easy to use simple unit tests to verify the code that manages your app state