Skip to content

Instantly share code, notes, and snippets.

Brian Vaughn bvaughn

Block or report user

Report or block bvaughn

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile

Pre-rendering virtual rows

Example list with ten total rows and a viewport large enough to display two rows.


█ - Visible row ▓ - Hidden/display-locked row ░ - Empty space (nothing rendered here)

View profiling-data.v2.json
"version": 2,
"profilingSummary": {
"commitDurations": [
bvaughn /
Last active Oct 10, 2019
Profiling a custom Chrome extension

Chrome's profiler ("Performance tab) is very useful for measuring JavaScript performance, but what if you want to measure the performance of a custom extension?

For example, what if I would like to profile the following interaction:

The interaction we want to profile

bvaughn / profile-data.json
Created Apr 1, 2019
Sample React DevTools profiling data export
View profile-data.json
"version": 1,
"profilingSummary": {
"commitDurations": [
bvaughn / example.jsx
Last active Aug 24, 2019
Advanced example for manually managing subscriptions in an async-safe way using hooks
View example.jsx
import React, { useMemo } from "react";
import useSubscription from "./useSubscription";
// In this example, "source" is an event dispatcher (e.g. an HTMLInputElement)
// but it could be anything that emits an event and has a readable current value.
function Example({ source }) {
// In order to avoid removing and re-adding subscriptions each time this hook is called,
// the parameters passed to this hook should be memoized.
const subscription = useMemo(
() => ({
bvaughn /
Last active Oct 12, 2019
Infinite lists and reflow

Infinite lists and reflow

In my experience, infinite lists use two basic layout strategies. The first uses absolute positioning to control where visible items are rendered. The second uses relative positioning (with top/left padding to offset for unrendered items).

In both cases, the list abstraction caches some metadata about the size of items once they have been rendered– so that it knows where to position the items that come after them.

Both of these strategies need to handle reflow. For example, changing the width of a list often affects the height of its itesm. Generally speaking, only the "window" of rendered (visible) items are remeasured in this case (because it would be too slow to rerender and remeasure all of the items before). But once a user scrolls backwards (up/left)– the list needs to account for the reflowed sizes. If it didn't, items would appear to jump up or down (depending on the delta between the previous, cached sizes and the new/reflowed sizes).

How the list deals with new sizes

View ReactNative-useEffect-repro.js
import React, {useEffect, useRef, useState} from 'react';
import {Animated, Text} from 'react-native';
// Begin
export const useAnimatedValue = initialValue => {
const ref = useRef(new Animated.Value(initialValue));
return ref.current;
const getInitialValue = config => {
if (typeof config.initialValue !== 'undefined') return config.initialValue;
bvaughn /
Last active Jul 12, 2019
react-window itemData -> data props behavior

Related discussion on bvaughn/react-window/issues/85.


The specific API feature this Gist is exploring is the itemData prop. This prop provides a way for a component to pass "contextual" list data to an item renderer without adding the overhead of using context. In most cases, a single value is passed (e.g. an array/list) like so:

function ComponentThatRendersAListOfItems({ itemsArray, }) {
  render() {
    // Pass items array to the item renderer component as itemData:
    return (
View App.js
import React, { Component, Fragment, Suspense } from 'react';
import read from './Resource';
// Wait long enough for DevTools to see
const wait = (ms = 1) => {
const startTime =;
while ( - startTime < ms) {
// ...
View test-error-boundaries.js
const jestDiff = require("jest-diff");
describe("error boundaries", () => {
let BrokenRender;
let DidCatchErrorBoundary;
let GetDerivedErrorBoundary;
let React;
let ReactNoop;
let ReactFeatureFlags;
let ReactTestRenderer;
You can’t perform that action at this time.