Thomas Junghans tjunghans

This is something a think about a lot. I a while ago I browsed the Pure ESM package gist by Sindresorhus and there's one point When should I use a default export or named exports?.

He suggests:

My general rule is that if something exports a single main thing, it should be a default export.

There's also this:

Why use default exports at all? Simplify usage: Having a default export simplifies import when the person importing the module just wants the obvious thing from there. There’s simply less syntax and typing to do.

	export enum ActionType {
	CreateSomething,
	UpdateSomething,
	DeleteSomething,
	RetrieveSomething
	}

	const isPortnumber = (value: number): boolean => {
	// https://en.wikipedia.org/wiki/Registered_port
	return value >= 0 && value <= 65535;
	};

	const isValidPortnumber = (value: unknown): value is number => {
	if (typeof value === "number") {
	return isPortnumber(value);
	}

	On xyz master branch run the following to get the count for the year 2024.

	git log --format="%h %an %Cgreen%as%Creset %d" --first-parent --tags --no-walk \| grep -c -e '2024'

	Omit “-c” to list the entries for 2024:

	git log --format="%h %an %Cgreen%as%Creset %d" --first-parent --tags --no-walk \| grep -e '2024'

	// Place this file inside <projectRoot>/__mocks__/react-query.js
	export const useQuery = jest
	.fn()
	.mockReturnValue({ data: {}, isLoading: false, error: {} });

	export class QueryClient {}

	import React, { type DetailedHTMLProps, type HTMLAttributes } from "react";

	export const createComponentMock = <
	T extends DetailedHTMLProps<HTMLAttributes<HTMLDivElement>, HTMLDivElement>
	>(
	componentName: string
	) => {
	const fakeComponent = (props: T) => (
	<div data-testid={componentName} {...props} />
	);

	// See https://gist.github.com/tjunghans/0129439ad12b37b98c72477156cddbce for the definition of `doSomethingAsync`.

	function MyComponent({ someprop }) {
	const [value, setValue] = React.useState("");

	React.useEffect(() => {
	// Create an instance of the AbortController that will
	// be used to abort in the useEffect return.
	const controller = new AbortController();

	// The implementation below is inspired by the [example](https://developer.mozilla.org/en-US/docs/Web/API/AbortSignal#examples)
	// that shows how a fetch operation can be aborted using the signal option.
	// See https://gist.github.com/tjunghans/da50cc29f3f965d587db99c2f44813f1 for an example on how `doSomethingAsync` is used.

	function doSomethingAsync(
	// payload can be anything. It's just an example
	payload,
	{ signal }: { signal?: AbortSignal } = {}
	): Promise<any> {
	// Abort immediately if `abort` was already called.

	# EditorConfig is awesome: https://editorconfig.org/

	root = true

	[*]
	charset = utf-8
	indent_style = space
	end_of_line = lf
	indent_size = 2
	insert_final_newline = true

	#!/usr/bin/env node

	const { readdir, writeFile } = require("fs");
	const { promisify } = require("util");

	function createDirEntry(dir) {
	return { name: dir, path: `packages/node_modules/${dir}` };
	}

	function createProjectCodeWorkspaceContents(dirs) {