Front-End Development and stuff …
Data mocking – Ways to fake a backend (API)
What are the advantages of working with fake data in projects with a clean separation between the frontend and the backend? How can we mock our backend with minimum effort? This blogpost will answer this questions and explains different methods of providing data via a dummy backend.
Switch Node.js versions with the Node Version Manager (nvm)
Sure you can just use homebrew to update your Node.js installation when there are new releases. It’s in fact very handy to do so. But beside the quirk when it comes to updating npm there is a method which makes switching Node.js version even easier. This became more important since the stable release of Node 4.0 which I like to use. But I have to be able to use a different Node version just in case thinks break with Node 4.0.
Quick Tip: Updating your node modules is easy as »1, 2, 3«
It might be a »no-brainer« in case you are working within the Node.js environment for a while. But I used to ask myself how to figure out if there are updates to my dependencies / devDependencies which are beyond the patch-level updates which are »automatically« installed via the definition within my `package.json`. Because I don’t like to check possible updates separately for every module I’m using in my project.
Quick Tip: Update your Git client on Mac OS X
I like to assist you just in case you wonder how to react on yesterdays announcement of that critical Git security vulnerability. As said within a post on Githubs Blog it’s strongly recommended to update your Git clients as soon as possible. Here we go with a short instruction how to update in case you are using OS X.