simonsmith

Resources

Newsletters

• https://web-design-weekly.com/
• https://react.statuscode.com/
• https://reactnewsletter.com/
• https://nodeweekly.com/
• https://javascriptweekly.com/
• https://frontendfoc.us/

simonsmith

const scripts = new Map<string, Promise<unknown>>();

export function fetchScript(
  src: string,
  additionalScriptAttrs: Record<string, string> = {}
): Promise<unknown> {
  if (scripts.has(src)) {
    // TypeScript cannot narrow down type with `has`
    // https://github.com/microsoft/TypeScript/issues/13086
    return scripts.get(src) as Promise<unknown>;

simonsmith

import {useState} from 'react';

export const requestStatus = {
  IDLE: 'IDLE',
  PENDING: 'PENDING',
  REJECTED: 'REJECTED',
  FULFILLED: 'FULFILLED',
};

export const useRequestStatus = () => {

simonsmith

import {retry} from './retry';

jest.spyOn(global, 'setTimeout');

test('retries a function and increases the backoff for each failure', async () => {
  const rejectingFunc = jest.fn(
    (() => {
      let failCount = 5;
      return () => {
        if (failCount === 0) {

simonsmith

#!/bin/bash

# Function to escape JSON strings
escape_json() {
    echo "$1" | sed 's/\\/\\\\/g; s/"/\\"/g' | sed ':a;N;$!ba;s/\n/\\n/g'
}

# Get git information
BRANCH=$(git symbolic-ref HEAD 2>/dev/null | sed 's/refs\/heads\///' || echo "unknown")
COMMIT_ID=$(git rev-parse HEAD 2>/dev/null || echo "unknown")

simonsmith

import {useEffect, useRef, RefObject} from 'react';
import {detectDevice} from '../../Atoms';

const styles = {
  'touch-action': 'none',
  overflow: 'hidden',
  'overscroll-behavior': 'none',
};

const iosStyles = {

simonsmith

//
/* You may copy+paste this file and use it as it is.
 *
 * If you make changes to your about:config while the program is running, the
 * changes will be overwritten by the user.js when the application restarts.
 *
 * To make lasting changes to preferences, you will have to edit the user.js.
 */

/****************************************************************************

simonsmith

Global instructions

Apply these rules everywhere, including chat, code comments, commit messages, and PR text.

Style

• Lead with the answer or action.
• Use plain, direct language. Prefer simple wording over jargon or formal phrasing.
• Be concise, but keep caveats and detail needed for correctness.
• Do not use preambles, filler, praise, or trailing offers.