The Drastic Effects of Omitting NODE_ENV in Your Express.js Applications
Most developers learn best by examples, which naturally tend to simplify
matters and omit things that aren't essential for understanding. This means
that the "Hello World" example, when used as starting point for an
application, may be not suitable for production scenarios at all.
I started using Node.js like that and I have to confess that it took me
almost two years to quantify the huge performance impact of omitting a single
environment variable. In fact it was just a coincidence that I even did it
right in my previous projects.
Mind your environment
Environment variables are often used for distinguishing between environments
like "production", "staging" and "development". Depending on those variables
an application may turn debugging on or off, connect to a specific database,
or listen on a... (more)
What You Need to Know About Node.js 4.0.0
Now - that Node.js 4.0.0 was officially released - you may wonder what it
delivers to you and if you should upgrade right away, or not. This post
covers the most important changes you need to know, and some key implications
you may have to take into account in making your decision.
The Story So Far
The last few months were really exciting for the Node.js community.
At the start of this year Joyent Inc. handed over the project to the
community around io.js, a fork of Node.js. Soon after that, it was decided
that there should be only one ver... (more)