In general, I strongly dislike debugging in Visual Studio Code, because it is a pain in the ass to configure for every project from the beginning, besides it sometimes simply doesn’t work.
One of the worst things to debug are unit tests running in Node.js. They run in weird threads, start with complicated frameworks, and often simply don’t hit breakpoints.
The worst so far was AVA.
…When installing packages to a Node.js project, many people stick with the default npm. Many people also use its alternative, yarn, but few know about more uncommon ones like pnpm or dry.
…Most of my Node.js projects require some build routine. As a fan of minimalism, for simple builds I used to write short scripts operating directly on fs. In order to avoid duplication and simplify the process for future, I created a simple npm package. I described the required steps below.
There are many frameworks for testing a Node.js project. Too many. And most of them require huge dependencies. Check the brief report below to find out.
…For simple build tasks in Node.js I use a custom script. Let’s consider the following requirements:
dist and dist/assets folders.dist/background-dist.js.assets/*.png files to dist/assets/.As a quick exercise, I wanted to read all URLs from my page’s sitemap instead of crawling the site. Just after I added a nested callback I decided to apply the Single Responsibility Principle and convert calls to Promises. Later I experimented with async/await and automatic conversion with Node’s promisify. Finally, I rewrote the solution in functional style using Ramda and reactive using RxJS. Read on to follow the evolution of callbacks in JavaScript.
…