Izhaki

The introduction to Reactive Programming you've been missing

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

Usage

Use latest Neo4j for best results, e.g. 2.2.2 or 2.3.0-M02 (http://neo4j.com/download) On a machine with 12 cores use concurrency 24

Create 1 node, 1 rel, 1 property per request, 1M requests

Total: 1M nodes, rels, props

Debugging ES6 in VS Code

My current editor of choice for all things related to Javascript and Node is VS Code, which I highly recommend. The other day I needed to hunt down a bug in one of my tests written in ES6, which at time of writing is not fully supported in Node. Shortly after, I found myself down the rabbit hole of debugging in VS Code and realized this isn't as straightforward as I thought initially. This short post summarizes the steps I took to make debugging ES6 in VS Code frictionless.

What doesn't work

My first approach was a launch configuration in launch.json mimicking tape -r babel-register ./path/to/testfile.js with babel configured to create inline sourcemaps in my package.json. The debugging started but breakpoints and stepping through the code in VS Code were a complete mess. Apparently, ad-hoc transpilation via babel-require-hook and inline sourcemaps do not work in VS Code. The same result for attaching (instead of launch) to `babel-node

How to add an image to a gist

Create or find a gist that you own.

Clone your gist (replace <hash> with your gist's hash):

# with ssh
git clone [email protected]:<hash>.git mygist

# with https

git clone https://gist.github.com/.git mygist

Travis CI - GitHub Satellite 2019

Is it going to be used as a dependency to a nodejs application that is not bundled? (e.g. command line utilities)
Is it going to be used as a dependency to a nodejs application that is bundled? (e.g. AWS Lambdas)
Is it going to be used as a dependency to a browser application (always bundled)?.

In cases 2) and 3) you want to allow for tree shaking.
In cases 1) and 2) you want to benefit from the "ES6"/"ES next" features supported natively by nodejs.
In case 3) you also want to benefit from the native support of "ES6" from your browser.

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

Use ESM yourself. (preferred)
Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
Stay on the existing version of the package until you can move to ESM.

	<!doctype html>
	<html lang="en">
	<head>
	<meta charset="utf-8">

	<title>
	{% if page.title %}
	{{ page.title }} \| {{ site.title }}
	{% else %}
	{{ site.title }}

	/**
	* @param {number[]} nums
	* @param {number} target
	* @return {number}
	*/
	var searchInsert = function(nums, target) {
	var start = 0;
	var end = nums.length - 1;
	var index = Math.floor((end - start) / 2) + start;