Here is an example of all three above. From what I know, the patterns are checked in order of how I coded them.
As I said, the first block handles my static stuff. I’ve specified a folder called public and inside of there I’d place my CSS and JS files. Once I drop in a style file I’d address it by just pointing the URL to /public/style.css.
The second block handles the home page request. Don’t worry about “blog” just yet, I’ll explain it in a bit. But basically, you can see that I’m calling for some data and then rendering it. (Again, more on that in a second.)
Finally - I added support for loading one particular blog entry. Note that I was able to precisely define a URL pattern of /entry/X. I could have done anything here at all. I love that freedom. To be clear, you can do the exact same in ColdFusion if you add in a URL rewriter like what’s built into Apache. But I like having it right here in my application. It makes it a bit easier to mentally grasp what is going on in the application.
If you visit my blog often, you know that I use a slightly slicker URL scheme. It took me then 5 minutes to add this to my application:
If you look at the app.get(“/”) block above, you can see where I run res.render(). The first argument is the name of a template to run. By default this will be in a subdirectory called views. The second argument is data I’m passing to the view. Here is what home.html looks like - and remember - I did this very fast and kinda ugly. Normally you would have a bit more HTML in there:
I am not a fan of the template syntax. Frankly it felt like I was writing classic ASP. That being said - it did work. Note that I’m doing a bit of work to create the fancy URL. EJS supports (I believe) writing your own helper functions. Normally I’d have built something to simplify that so that the view had much less logic in it. Just assume that as my first view I didn’t write this as nicely as I would if given more time. As a comparison, here is the view for an individual blog entry:
As I mentioned, I’m not really a fan of EJS. There are other alternatives. Right now I’m considering Dust, but as I ran into problems with that, I couldn’t actually use it.
Hopefully at this point you have a rough feel for how Express lets you handle requests and specify views to actually render them. Let’s talk about the database layer. After I figured out how to do my views and pass parameters around, I needed to get database support. This is where I got to play around more with NPM. NPM, or the Node Package Manager, is an incredibly powerful tool and probably one of the main reasons Node is so popular. (Other platforms have similar support.) From the command line you can tell Node to get a package (think open source project focused on adding a particular feature) and install it to your system. You can also tell your application itself that it requires a package. So for example, my application needs Express and MySQL support. I can use a special file (package.json) to note these requirements, run one command, and all the supporting libraries just magically come in.
But… this isn’t all rainbows and unicorns. When I decided to add RSS support to my application, I used NPM to search for an RSS library. If I remember right, about 30 or so packages showed up. I froze like a deer in headlights. Don’t get me wrong, I like options, but I had absolutely no idea which one to pick. This is very much like the problem you may have with jQuery plugins. You can almost always count on jQuery having a plugin to do X, but finding out what the “best” one is can be a laborious process. I feel like I’m going to get some criticism on this, but I do wish people would keep this in mind when praising Node. For me, I picked the package with the name “rss” just because it had the simplest name. Luckily, the one I chose worked great. I was able to add RSS support soon after:
With all that being said, using MySQL was pretty easy. I began by just setting up the connection like so:
I then created a module called blog that would handle my service layer. Since I had a “con” object that represented my database connection, I exposed an API where I could pass it in to the blog:
Here then is my blog module. A ‘real’ blog engine would have quite a bit more of course but you get the idea.
So what do I think? I love it. Once I got my environment running (and be sure to use nodemon to make reloading automatic) I was able to rapidly build out a simple application. I loved the level of control I had over the request and how quick it was to get up and running. I didn’t love the fact that the quality wasn’t quite consistent across various modules.
p.s. One more code snippet. I demonstrated the RSS support above. But I also built in a quick JSON view as well. It was incredibly difficult. Honest. This took me hours to write. (Heh…)