You’ll notice from time-to-time that Node.js will release a new minor version and sometimes a major version. If you’re working with TypeScript, you’ll want to install the @types/node typings into your project.
If you’re running Node.js version 12.14.1 confusion might set in because there is no matching version for the Node types package.
Node is known to introduce new features into minor releases, so ensuring that your typings are up-to-date within the latest major release band will ensure that your typings are not too old or too far forward (LTS vs current release).
Whilst doing some work in a library I maintain, I needed to add in the ability to calculate the hash of an included file for an integrity check feature I was adding in. The resulting solution is simple and not boast-worthy, but given others might encounter a situation where they need a hash of a file, this might help.
We use the fs module to open up the file we want to calculate the hash for, use the createHash method on the crypto package to then pass in our file buffer from the readFileSync method, and that’s it.
In Npm version 3 we finally got what we had been asking for the last few years: a flattened module structure for Node modules. Unfortunately as a result Npm has slowed to a crawl when installing or updating Node modules, well mostly just installing.
Recently it was circulating that disabling the progress bar resulted in at least a three times speed increase. I first saw it on Twitter and dismissed it initially.
If you were a startup trying to get an MVP out the door in 2010, admittedly you probably used or considered Ruby on Rails. In 2015 you are probably more than likely going to opt for Node.js instead. But why?
Once upon a time it seemed as if Ruby on Rails was destined for global dominance. Twitter was originally built on top of it before moving for scalability and performance reasons, but many companies still use Ruby on Rails.
If you are like me you not only develop in PHP, but you also dabble in other languages like Javascript and Node.js, then this blog post is for you. I like to write API servers in Node.js and interface with them in my AngularJS applications.
Because MAMP Pro comes with a useful feature of allowing easy hosts/URL aliasing creation, we can create a virtual URL for our API and then interact with it in our applications.