Free AI web copilot to create summaries, insights and extended knowledge, download it at here

1543

Abstract

Awilix is such a container, and it is implemented with <b>ES6 Proxies, which means no more string parsing of function parameters!</b></p><blockquote id="e1b4"><p><b>Update</b>: Awilix now supports (optional) classic injection which does parse the function parameters, and the parser is not just a shoddy regex but a purpose-built parser which <a href="https://github.com/jeffijoe/awilix/blob/e3181da0a668234141322b8970be097d0d19913c/src/__tests__/param-parser.test.ts#L149-L170">works pretty well</a>.</p></blockquote><p id="062d">So back to our app — let’s try stitching our system together using Awilix! We will be using Koa 2 for the web API, so lets install the modules we need.</p><div id="939b"><pre><span class="hljs-built_in">npm</span> install -S koa@next koa-router@next awilix awilix-koa</pre></div><p id="bfa3">The <i>awilix-koa</i> package makes Awilix even easier to use for Koa. Alrighty, let’s start by writing our composition root.</p><h2 id="a89b">configureContainer.js</h2> <figure id="e2e4"> <div> <div>

            <iframe class="gist-iframe" src="/gist/jeffijoe/d9a4ea3a45ffda376ad978c94eb8c401.js" allowfullscreen="" frameborder="0" height="undefined" width="undefined">
          </div>
        </div>
    </figure></iframe></div></div></figure><p id="6c30">That actually looks pretty good if you ask me. Don’t worry, if you have 100+ services you want to register, <a href="https://github.com/jeffijoe/awilix#auto-loading-modules">Awilix can automate

Options

this for you</a>, just check out the docs later. :)</p><p id="965e">Now lets configure our Koa app! It’ll be the I/O of our system!</p><h2 id="8f4f">server.js</h2> <figure id="6af1"> <div> <div>

            <iframe class="gist-iframe" src="/gist/jeffijoe/828b810d88c74449492bbc3bb9efa9cb.js" allowfullscreen="" frameborder="0" height="undefined" width="undefined">
          </div>
        </div>
    </figure></iframe></div></div></figure><p id="e8ea">That sure was a mouthful, but now you have a foundation for building <i>large scale unit testable apps</i> with less chance of shooting yourself in the foot.</p><h1 id="3dd5">Conclusion</h1><p id="091d">Dependency injection is a thing, but it sucks doing it manually. This can be solved by using a DI container (e.g. <a href="https://github.com/jeffijoe/awilix">Awilix</a>) — I may be biased as to what container to use given I wrote Awilix. ;)</p><p id="311a">DI will let us write our application code with total disregard for web frameworks — <i>or the environment for that matter</i>. The application code could be stuffed into a CLI or an Electron app if we wanted to, it’s totally portable! That’s the beauty of decoupling the application code from the web server code.</p><p id="3d50">I hope this article has opened your eyes to the world of doing dependency injection in Node, and that in 2016 it’s actually very doable.</p><p id="8772"><i>P.S. This is my first Medium story. How did I do? :)</i></p></article></body>

Dependency Injection in Node.js - 2016 edition, part 3

This is part 3 of a 3-part series on Dependency Injection in Node.

Part 1
Part 2
Part 3

No! This can’t be the end! There must be a way!

Angular was (AFAIK) one of the first big frameworks to introduce DI to the JavaScript world. Their approach was to use the function’s string representation and extract the names of modules that were being used. At the time that was the only way to do it.

Attempts have been made at separating the DI machinery from Angular to a separate module, but the problem is most DI modules requires all your code to cater to their specific DI system. That contradicts the very idea behind DI, and should be avoided at all costs.

We want to use DI with our service and repository without modifying their code.

Enter Awilix — the DI container you deserve.

If you don’t know what a DI container is, here’s a quick explanation. The DI container’s job is to stitch things together so that you, dear developer, won’t have to. All the plumbing code above: instantiating the services and repositories, making sure that the service gets the repository instance. All of that is done by a DI container.

Awilix is such a container, and it is implemented with ES6 Proxies, which means no more string parsing of function parameters!

Update: Awilix now supports (optional) classic injection which does parse the function parameters, and the parser is not just a shoddy regex but a purpose-built parser which works pretty well.

So back to our app — let’s try stitching our system together using Awilix! We will be using Koa 2 for the web API, so lets install the modules we need.

npm install -S koa@next koa-router@next awilix awilix-koa

The awilix-koa package makes Awilix even easier to use for Koa. Alrighty, let’s start by writing our composition root.

configureContainer.js

That actually looks pretty good if you ask me. Don’t worry, if you have 100+ services you want to register, Awilix can automate this for you, just check out the docs later. :)

Now lets configure our Koa app! It’ll be the I/O of our system!

server.js

That sure was a mouthful, but now you have a foundation for building large scale unit testable apps with less chance of shooting yourself in the foot.

Conclusion

Dependency injection is a thing, but it sucks doing it manually. This can be solved by using a DI container (e.g. Awilix) — I may be biased as to what container to use given I wrote Awilix. ;)

DI will let us write our application code with total disregard for web frameworks — or the environment for that matter. The application code could be stuffed into a CLI or an Electron app if we wanted to, it’s totally portable! That’s the beauty of decoupling the application code from the web server code.

I hope this article has opened your eyes to the world of doing dependency injection in Node, and that in 2016 it’s actually very doable.

P.S. This is my first Medium story. How did I do? :)