There is great number of differences between object literals and functions as constructors. You can have only one instance of object literal, while using function as a constructor you can have as much as you want. You don't have a constructor when using object literals, so if you want to initialize your object you probably want to have some function in object literal that will initialize your object (init, boostrap etc.). Object literal's type is Object, while function as constructor is Function, which means that they have different Prototype object linked on first step in prototype chain (Function.prototype will point to Object.prototype). For every function that you create, there is a new object created called Prototype and function is linked to it with prototype property, while when using object literal you don't get that unique prototype object, it's connected directly to Object.prototype. For usage purposes, I personally use object literals when I want to have only one instance of that object. Good example is config object (you shouldn't have more config objects in your app). The simplest way to create singleton pattern in JavaScript is using object literals. On the other hand, I would use function as constructor if I need multiple instances of one function. Good example are domain object (User, Task etc.). Hope that this helps a bit.

That is also the way I do it, npms.io is great service.

Yes, that helped me a lot to understand why everything needs to be written in asynchronous fashion. That differs from PHP where you write in synchronous fashion and you don't think about it. Take a look at this video: https://www.youtube.com/watch?v=8aGhZQkoFbQ It explains what's event loop quite good.

I come from PHP world, and I started working with NodeJS one and half years ago. Of course, you should first learn JavaScript as a language but you don't have to be master of it to work with NodeJS. Main thing that helped me understand how NodeJS works is when I learned about event loop and single thread principle. When you work with PHP you don't have to think about that because either Apache or PHP fpm handles that for you, and in Node you have to think about it all the time. Good luck!

I have been working with JavaScript for couple of years now, but only got to fully understand how JavaScript works when I read "You don't know JS" series by Kyle Simpson. In there you will find detail explanation on scope, this binding, prototype, async JS, performance, types and ES6. Although I admit that Kyle has some thoughts on his own on some of JavaScript features, this series gave me ability to fully understand and work with JavaScript in any environment, client, server and hybrid. Can't recommend it more!