Tomáš Horáček heracek

Building NW.js on macOS (for Mere Mortals) {: .doctitle}

This is an annotated version of Building NW.js from the official NW.js developer documentation. It includes my experience from building NW.js binaries for macOS, both Intel (x86-64) and M1 (arm64). The latter can be easily discerned since they are block-quoted and appear in red¹.

Not on GitHub though; they aggressively sanitize HTML in Markdown. Block quotes still work 😬 ↩

This example demonstrates how to polyfill the "fetch" event in Deno, and gives an example for how this can be used to run Cloudflare Workers in Deno.

To try it locally run the script below, and visit http://0.0.0.0:8080:

$ deno run --allow-net https://gist.githubusercontent.com/lucacasonato/1a30a4fa6ef6c053a93f271675ef93fc/raw/efcdc8e798604e194831830fcb962b50261384b3/example-worker.js

Replacing Create React App with the Next.js CLI

How dare you make a jab at Create React App!?

Firstly, Create React App is good. But it's a very rigid CLI, primarily designed for projects that require very little to no configuration. This makes it great for beginners and simple projects but unfortunately, this means that it's pretty non-extensible. Despite the involvement from big names and a ton of great devs, it has left me wanting a much better developer experience with a lot more polish when it comes to hot reloading, babel configuration, webpack configuration, etc. It's definitely simple and good, but not amazing.

Now, compare that experience to Next.js which for starters has a much larger team behind it provided by a world-class company (Vercel) who are all financially dedicated to making it the best DX you could imagine to build any React application. Next.js is the 💣-diggity. It has amazing docs, great support, can grow with your requirements into SSR or static site generation, etc.

So why

Explainer: Font Metrics Override Descriptors

(A newer version is at here, where a new descriptor advance-override is added)

Spec

This doc explains descriptors ascent-override, descent-override and line-gap-override for CSS @font-face rule.

Basic usage:

⚠️ I'd recommend using this fork by @igoro00 which has better theme support.

Tiny wrapper component for React-Datepicker to stylistically fit with Chakra-UI 1.x.

<DatePicker selectedDate={myDate} onChange={(d) => console.log(d)} />

Boolean() or !! (double bang, double negation)?

What's the best way to answer the question "true or false?" in JavaScript

JavaScript does not bother you too much with types (at first), which is both a blessing and a cure. But we all know the Boolean type. Boolean variables can either be true or false. Yes or no.

Every value in JavaScript can be translated into a boolean, true or false. Values that translate to true are truthy, values that translate to false are falsy. Simple.

This is about two ways to make that translation.

`Option` vs non-`Option`

	`Option<T>`	non-`Option` (`T \| undefined`)
accessing property	`userOption.map(user => user.age)`	`userNullish?.age`
calling a method	`userOption.map(user => user.fn())`	`userNullish?.fn()`
providing fallback	`ageOption.getOrElse(0)`	`ageNullish ?? 0`
filter	`ageOption.filter(checkIsOddNumber)`	`ageNull

	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
	<plist version="1.0">
	<dict>
	<!-- not sure which one it is, so set both -->
	<key>Ensemble</key>
	<dict>
	<key>Enabled</key>
	<true/>
	</dict>

	const { exec } = require('child_process');
	const { promisify } = require('util');
	const path = require('path');

	module.exports.default = async function tsc(options, context) {
	process.chdir(
	path.join(context.cwd, context.workspace.projects[context.projectName].root)
	);

	try {

	//
	// TextStyle.swift
	//
	// Created by Rob Napier on 12/20/19.
	// Copyright © 2019 Rob Napier. All rights reserved.
	//

	import SwiftUI

	public struct TextStyle {