this seems like a very very minor thing compared to correctly understanding how a bug in a screen showing "unauthorized access" on the react frontend project, is in fact triggered by a wrong configuration in a "authorization service" in a file located completely elsewhere, due to a serialization issue, etc..
"visualizing a general architecture" is piece of cake compared to the mental model one need to understand a full stack react / express / sqlite / typescript stack with sufficient details to be able to debug obscure error code.
"visualizing a general architecture" is piece of cake compared to the mental model one need to understand a full stack react / express / sqlite / typescript stack with sufficient details to be able to debug obscure error code.