We run our protractor tests in Chrome instance via xvfb server. Last week after Chrome update to 60.0.3112.90, it began to fail with the following error. The solution was to use an older version of Chrome driver for Selenium, via the following command:
Few days ago I decided to find a Stopwatch app for my Mac. I went over to the App Store and noticed that there were no good free options available. I thought to myself, how hard would it be to make one with Electron? Turns out, it was very easy. Getting an Electron shell running … Read more
Guillermo Rauch (Socket.io, Mangoose.js, Hyper.js, Now) is the guy to watch, and last night he did not disappoint. The following tweet announced pkg – a simple tool to generate a native executable file from Node.js code targeting Mac, Linux, and Windows. Introducing `pkg` Single command binary compilation for Node.js pic.twitter.com/Dbe9L1gb0x — ZEIT (@zeithq) April 29, … Read more
Introduction I am not an expert on either of the package managers. Contrary, until few days ago I didn’t realize that npm used a local cache. Unaware, I wrote an article titled OMG — NPM clone that finally makes sense and was called out on some of my false assumptions. That feedback forced me to take a … Read more
Note: Everything I’ve assumed was wrong, I am keeping track of things as I discover them via the medium post: https://medium.com/@akras14/omg-npm-clone-that-finally-makes-sense-3478588879 I’ll update this post when the dust settles 🙂 Last week I came across a yet another NPM clone, called pnpm, but unlike other clones (cough Yarn) this one is actually interesting! What so … Read more
A few weeks ago our production code started to throw a weird error, that looked like this: This was very strange, since it was coming from a code that used to work for a long time. The only thing that has changed was the Node version. I’ve tried Googling for the issue, but all I … Read more
Table of Contents Introduction Minimal Theory Step 1. Reproduce and confirm the problem Step 2. Take at least 3 Heap dumps Step 3. Find the problem Step 4. Confirm that the issue is resolved Links to some other resources Summary Something you might want to bookmark: Simple Guide to Finding a JavaScript Memory Leak in … Read more
I needed a simple server to test my HTTPS POST requests. Just like a regular HTTP server, it is super easy to do in Node. Except I needed to add private key and a cert, which is an extra step and was not immediately obvious to me, so I figure I’d share my findings. Step … Read more
Run it as sudo i.e. I just spent over 10 minutes looking around the internet for this simple solution. Hopefully, this post will save somebody some time 🙂