Dane Wilson danew

The experience of using Node.JS with TypeScript, ts-node, and ESM is horrible.

There are countless guides of how to integrate them, but none of them seem to work.

Here's what worked for me.

Just add the following files and run npm run dev. You'll be good to go!

`package.json`

Forking and patching npm modules from a monorepo

Commonly, npm modules are source controlled using a single dedicated repo for each module. When forking and patching such an existing npm module, typical approaches are either:

reference a specific git commit in your forked repo

    "dependencies": {
        "patchedmodule": "git+https://github.com/myuser/patchedmodule.git#mypatch"
    }

reference a downloadable tarball containing the same, as described in this post on {debuggable}

Important: At the time of writing (2019-11-11) Immutable.js is effectively abandonware, so I can no longer recommend anyone to follow the advice given here. I'll leave the article here for posterity, since it's still getting some traffic.

Understanding Immutable.Record

Functional programming principles and with it immutable data are changing the way we write frontend applications. If the recent de-facto frontend stack of React and Redux feels like it goes perfectly together with immutable data, that's because it's specifically designed for that.

There's several interesting implementations of immutable data for JavaScript, but here I'll be focusing on Facebook's own Immutable.js, and specifically on one of i

	/* eslint-disable no-console */
	/***
	* This is a little server that emulates the protocol used by cloudflare's browser rendering API. In
	* local development, you can run this server, and connect to it instead of cloudflare's (strictly
	* limited) API. e.g. in your worker you might use a function like this:
	*
	* ```ts
	* import { Browser, launch as launchPuppeteer } from '@cloudflare/puppeteer'
	* function launchBrowser(env: Environment) {
	* if (env.LOCAL_BROWSER_ORIGIN) {

	{
	"name": "remove-ts",
	"version": "1.0.0",
	"description": "I use this to automatically fix feedback links in my workshops",
	"bin": "./remove-ts.js",
	"dependencies": {
	"@babel/core": "7.13.8",
	"@babel/preset-typescript": "7.13.0",
	"glob": "7.1.6"
	}

	class Frame extends Component {
	componentDidMount() {
	this.iframeHead = this.node.contentDocument.head
	this.iframeRoot = this.node.contentDocument.body
	this.forceUpdate()
	}

	render() {
	const { children, head, ...rest } = this.props
	return (

	/* bling.js */
	window.$ = document.querySelector.bind(document);
	window.$$ = document.querySelectorAll.bind(document);
	Node.prototype.on = window.on = function(name, fn) { this.addEventListener(name, fn); };
	NodeList.prototype.__proto__ = Array.prototype;
	NodeList.prototype.on = function(name, fn) { this.forEach((elem) => elem.on(name, fn)); };

	# I've always disliked the "./configure" incantation - it's right here! I
	# shouldn't need to tell the shell where to look for it. But of course,
	# putting '.' in your $PATH is terrible -- it's insecure and throws permission
	# errors if you try to 'execute' regular files. Bash 4's `shopt -s autocd`
	# solves half the problem; and the ability to override
	# command_not_found_handle() solves the other.
	#
	# This is an OS X-oriented script that attempts to do the most intelligent
	# thing possible when you enter the name of a file in your $PWD into the bash
	# prompt. It will:

	###### .env ######
	EDGEDB_USER="my_user"
	EDGEDB_PASSWORD="my_password"

	{
	"ru": {
	"Your original english text": "Твой оригинальный русский текст"
	}
	}