re: When and Why you should do Dependency Injection in React VIEW POST


I have few remarks to your article:

The typical module system in JavaScript has a caching mechanism.

Typical module system in NodeJS, not JavaScript. This doesn't work that way on the browser.

What this means is that we can initialize our dependencies and it will be cached and we can inject it in multiple places without loading it again. We are creating a Singleton when we are exporting this module.

Even in NodeJS, this is not a best practice, as it can be easily broken. Check out this article.

And one more: I think it's not a good idea to use the Context API for injecting things like a websocket service. Context API is for passing data through the component tree, I guess that passing complicated objects out there might create problems (i.e. performance ones). For things like this - why not just import it?


Hey Jakub, that is a great feedback. Thank you for the input. I will do some more research on the module system. I have been injecting services like simple websockets and firebase real time DB instances through Context. And I totally agree if not careful these will lead to memory leaks. I will do some more research on these as well and definitely address these caveats. Good feedback though. Loved it :)

code of conduct - report abuse