AndrewIngram

import { useRef, useCallback, useInsertionEffect } from "react";

// Approximation of React's upcoming useEffectEvent hook
// This gives us a non-reactive effect event callback, it will always use the latest version of
// the callback, rather than the one that was closed over.
export default function useEffectEventShim<T extends (...args: any[]) => any>(
  fn: T
): (...funcArgs: Parameters<T>) => ReturnType<T> {
  const ref = useRef(fn);

AndrewIngram

A simple sketch of how we migrate a "card" component to lazy-load its popover content by server actions. The after (lazy) version is visibly more complex, but the steps involved are fairly straightforward -- and if it were a common pattern, there are steps that could be taken to abstract it into something simpler.

Important to note that if it's determined that server actions can only be defined in server components, the solution would be a little different.

AndrewIngram

import { AwsClient } from "aws4fetch";
import { deflate } from "pako";

const R2_ACCOUNT_ID = "SOMETHING"
const R2_ACCESS_KEY_ID = "SOMETHING"
const R2_SECRET_ACCESS_KEY ="SOMETHING"
const R2_BUCKET = "SOMETHING"
const R2_URL = `https://${R2_BUCKET}.${R2_ACCOUNT_ID}.r2.cloudflarestorage.com`;

AndrewIngram

import { SitemapStream, EnumChangefreq } from "sitemap";

import { getAllPosts } from "~/data";

import { Readable } from "node:stream";

async function* getSitemapUrls(request: Request) {
  const url = new URL(request.url);
  const origin = `${url.protocol}//${url.host}`;

AndrewIngram

import { SitemapStream, EnumChangefreq, streamToPromise } from "sitemap";

import { getAllPosts } from "~/data";

import { Readable } from "stream";

async function* getSitemapUrls(request: Request) {
  const url = new URL(request.url);
  const origin = `${url.protocol}//${url.host}`;

AndrewIngram

import { use } from "react";

type Props<T> = {
  resolve: Promise<T>;
  children: (value: T) => React.ReactElement;
};

export default function Await<T>({ resolve, children }: Props<T>) {
  const value = use(resolve);

AndrewIngram

Warning, this is a bad idea. It'll eventually break and use undocumented framework internals

Using headers() and cache() in Next 13.1 API routes

Note: API routes are still only supported in the pages folder, not app.

I was playing around with using API routes with the experimental app dir stuff in Next 13, and I was frustrated at having to use completely different code paths for accessing the request headers and cookies compared to in server components. So I hacked together a workaround which you definitely shouldn't use.

Usage requires two steps, one is easy, the other is invasive:

AndrewIngram

"""
This snippet will return all the letting agents, bucketed into discrete bands based on distance from
an origin point (for example, the user's current location), then sorted alphabetically within each
band. The goal being to prioritise agents in close proximity, but not excessively so -- all agents
within the same band should be given equal distance-related priority.

If there's a search term, we then boost the distance score based on the name's similiarity to the
search query.
"""
qs = LettingAgentLocation.objects.select_related("agent").filter(postcode__isnull=False)

AndrewIngram

import { mergeWith } from "lodash";

export function nullPrototypeFix(object: Object): Object {
  return mergeWith({}, object, (a: any, b: any) => {
    if (b === null || typeof b === "undefined") {
      return b;
    } else if (typeof b.toJSON == "function") {
      return b.toJSON();
    }
  });

AndrewIngram

function getIsLiked(viewerId, entityId) {
  // hit a database or something
}

function toggleLikeStatus(viewerId, entityId) {
  // hit a database or something
  return !currentStatus;
}