I am very happy to announce a brand new project of mine called Developer’s Notebook, a blog and news website with content for developers.
Trying out a new technology can be a bit tricky, so a set of specs for a test app is necessary to give the tests meaning.
Since I am constantly starting a new project, I got tired of always having to set up each web app from scratch. Therefore, I decided to create a couple of boilerplate apps in Node.js and TypeScript.
I recently wrote a small script using TypeScript that can be used to determine the size of the view port using the breakpoints as defined by Bootstrap.
For about two years I have been using Grunt to compile my SASS files into CSS for projects for work as well as for personal projects such as this website. This workflow has served me well and I still use it for most of my PHP-based projects. However, I’ve come up with an even easier and faster solution for my Node.js-based applications.
A couple of months ago, I joined a band called Future Sequence on the bass.
Node.js + Docker + WebStorm is not an unusual setup for Node.js developers, but there is nonetheless surprisingly little information available about how to setup debugging in WebStorm while running a Node.js application locally in a Docker image.
When using a combination of Express and krakenjs in your Node.js application, there is a feature enabled by default which automatically leads to a nasty memory leak.