Drew Lustro drewlustro

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.

Setting up Jest with ESM

Here are some different ways on how to set up Jest to support ESM. This applies for Jest v25, Node v13, and Babel v7.

Method A: Native Node.js support

Node v14 and Jest v26 support ESM natively with the --experimental-vm-modules flag.

Install cross-env:

Prerequisites

The app that uses tailwind + external component library (CL) (but not 3rdparty, your company internal one, for example)
The component library also uses tailwind

The goal

To be able to purge safely unused tailwind classes from the build (https://tailwindcss.com/docs/controlling-file-size)

Solution

The idea here is simple: we're going to purge css on the app side + whitelist classes that component library is using.

I am assuming you are here because like me, you installed a bazillion different python interpreters on mac and the whole thing is a spagetti. Today, I finally fixed my python installation. Whatever I install for python2 or python3 using pip JUST.WORKS.. My god! finally.

What the hell?

Here is what I had messed up, which you also probably did:

I had too many different python interpreters
Too many different symlinks which I lost track of
almost no package I installed with pip worked without a headache
any attempt to fix using online resources made it worse.

Faster Rails tests

Feedback loop speed in one of the biggest contributing factors to overall development time. The faster you get results, the faster you can move on to other things. A fast enough test suite is therefore critical to teams' success, and is worth investing some time at the beginning to save in the long run.

Below is a list of techniques for speeding up a Rails test suite. It is not comprehensive, but should definitely provide some quick wins. This list of techniques assumes you're using minitest, but most everything should translate over to rspec by simply replacing test/test_helper.rb with spec/spec_helper.rb.

Lead with data
bcrypt
bootsnap
Cache Time::utc calls

	<!DOCTYPE html>
	<html>
	<head>
	...
	</head>

	<body data-controller="js">
	<%= yield %>
	</body>
	</html>

	import jscodeshift from "jscodeshift";
	import fs from "fs";
	import path from "path";

	const projectDirectory = "my/project/root/directory";

	///////////////////////////////////////////////////////////////////////////////
	// util functions
	///////////////////////////////////////////////////////////////////////////////

	/**
	* NOTE: this specifically works if the house is for sale since it renders differently.
	* This will download the highest resolution available per image.
	*/



	/**
	* STEP 1: Make sure to SCROLL through all images so they appear on DOM.
	* No need to click any images.

	var $ = require('nodobjc')

	$.framework('Foundation')
	$.framework('AppKit')

	var GetSongs = $.NSObject.extend('Delegate');

	GetSongs.addMethod('getMySongs:', 'v@:@', function(self, _cmd, notif){
	var userInfo = notif('userInfo')
	var keys = userInfo('keyEnumerator');