Three Ways to Provide (TypeScript) Type Definitions to Open-Source Libraries

Three Ways to Provide (TypeScript) Type Definitions to Open-Source Libraries July 22, 2017

Even though the library of type definitions is vast, the amount of JavaScript libraries is even greater. Every TypeScript developer will encounter a situation where the

Yarn vs. npm: Installation Time

Yarn vs. npm: Installation Time November 02, 2016

Yarn is a client for the npm registry, Node.js ecosystem for the packages. This new client will address performance, reliability, and security-related issues. Before diving

NPM-Gate: Seeking constructive criticism, finding joke sites and arrogance

NPM-Gate: Seeking constructive criticism, finding joke sites and arrogance March 27, 2016

If you haven't heard about so-called NPM-gate, then please read one of the summaries of the topic (Ars Technica, npm blog or Business Insider). As a

Migrating medium-sized project to Node 4

Migrating medium-sized project to Node 4 October 11, 2015

With all the confusion with io.js has been settled, and epic merge has been done, it's time to upgrade your current project. To bring a

NPM network and proxy related error

NPM network and proxy related error September 11, 2015

There is a network related error that I stumble upon quite often. The weird thing is that this occurs in a non-corporate networks such as my

npm 3 will bring brighter future for Windows users

npm 3 will bring brighter future for Windows users August 07, 2015

Around 40% of the npm users are using Windows. It is a big chunk but unfortunately, there has been long-running Windows specific issues that have caused

Avoiding unnecessary Gulp plugins

Avoiding unnecessary Gulp plugins July 16, 2015

There are many cases where Gulp plugins are not necessary and can cause more problems than real benefits. Let's take gulp-kss as an example. It is

How node package deprecation works

How node package deprecation works April 10, 2015

You have probably encountered a warning message saying: "npm WARN deprecated packageX: Use packageY instead, see {link to the repository/web-site}". This warning is displayed because