No, it’s not safe to utilize. That’s why it has a frightening name. We provide no warranties about what will take place if you access things there. The habits can alter on any release. We highly suggest versus touching it in your library if you do not desire that library to break later.
I might alert the user the name of the element that took in a custom-made hook without covering it with needed context.
If you utilize console.error and the user has React DevTools then they need to currently see the part stack in advancement instantly. That’s the desired service.
is it safe to utilize in production? This usage case.
No, the connected response will most absolutely break. It’s unclear to me what was the initial issue that the author attempted to resolve, however there are usually much better methods to approach it.