ashley williams ashleygwilliams

Minimal example making webpack and wasm/Emscripten work together.

Build instructions:

Clone this gist
npm install
npm start
Open http://localhost:8080
Look at console

Zero One Infinity READMEs

npm has only been a company for 3 years, but it has been a code base for around 5–6 years. Much of it has been rewritten, but the cores of the CLI and registry are still the original code. Having only worked at npm for a year at this point, there’s still a lot of things left for me to learn about how the whole system works.

Sometimes, a user files a bug which, in the process of debugging it, teaches you some things you didn’t know about your own system. This is the story of one of those bugs.

The Bug

Over the past week or so, [several][1] [people][2] [filed issues][3] regarding some strange truncating in npm package pages. In one issue, a user reported what appeared to be a broken link in their README:

___an infinite space

45 ways to visualize two numbers http://blog.visual.ly/45-ways-to-communicate-two-quantities/

___navigating the infinite space

knights movement:

	#!/bin/bash
	# REQUIRES SUDO
	# Benchmark runner

	repeats=20
	output_file='benchmark_results.csv'
	command_to_run='echo 1'

	run_tests() {
	# --------------------------------------------------------------------------

	var express = require('express');
	var taters = require('taters');
	var enchilada = require('enchilada');
	var makeup = require('makeup');
	var veto = require('veto');
	var browserkthx = require('browserkthx');

	// we set certain settings based on production or not
	var kProduction = process.env.NODE_ENV === 'production';