In fact, that idea is what I want to talk about.
It is very easy to get caught up in the never-ending spiral of “this tool doesn’t do X, so I will get tool Y to fix that”. Having an ecosystem with all sorts of tools for almost any problem is a blessing and a curse. It’s great to have access to so many good libraries, but a growing list of dependencies often is more work than necessary. Moderation is key.
At the core of this issue is the idea that you have to use the latest, greatest, and “sexiest” frameworks in every single project you do. This is a very naive approach to coding, in general.
There are plenty of adages and sayings against dependency creep (e.g. “less is more”, “keep it simple, stupid”). Basically, only include dependencies that you know will have positive returns on your development time and effort. Don’t just blindly use a library because it’s new or popular.
However, maybe that means it is worth looking into. Just keep in mind that you’ll need some time to learn the tool. You may even need to learn the tool just to determine if it helps you. If that’s the case, make sure you aren’t treating everything like a nail with your new hammer.
If you are completely new to the ecosystem, it can be hard to determine a simple set of dependencies that will have those high returns.
Below is a list (in order!) of basic tools you should start with. I will try to include the name of appropriate “workshoppers” from NodeSchool. A workshopper is a collection of lessons that require you to do a small lab after each lesson. This practice is crucial for actually learning material.
I highly recommend reading
This is by far the most common Node module for setting up REST services. Express allows you to set up basic routes using a fantastic yet simple API.
Mocha is a test runner (so for actually setting up and running the tests). Chai is an assertion library, which means it is used to do the actual checks (e.g. to make sure a return value is a number greater than 0). Just by using these two, you have a very powerful unit testing framework.
If you need code coverage, you can set up Istanbul to run with mocha. You don’t really have to learn much for Istanbul.
UPDATE: Probably just use Jest (https://facebook.github.io/jest/).
UPDATE: Personal preference learning is leaning towards React, now that it is MIT licensed.