developit

if (typeof window!=='undefined' && navigator.serviceWorker && navigator.serviceWorker.controller) {
	let reloadOnNext = false;

	let pushState = history.pushState;
	history.pushState = function(state, title, url) {
		pushState.call(this, state, title, url);
		if (reloadOnNext===true) location.reload(true);
	};

	navigator.serviceWorker.controller.addEventListener('statechange', e => {

trueadm

// Option C:
// this implementation has a small amount of overhead compared to (a) and (b)
const React = require('react');

const counterState = React.createStateReducer({
  initialState: props => ({
    counter: 0,
    divRef: React.createRef(),
  }),  
  reducer: (action, state) => {

threepointone

A series of posts on css-in-js

0. styles as objects

First, an exercise. Can we represent all of css with plain data? Let's try.

let redText = { color: 'red' };

leebyron

/**
 * For compare function return:
 * - Less than zero: item1 has higher priority than item2.
 * - Zero: same.
 * - Greater than zero: item1 has lower priority than item2.
 */
export type CompareFunction<T> = (item1: T, item2: T) => number;

export class PriorityQueue<T> {
  _items: Array<T>;

bvaughn

This API was removed in React 17

---

Interaction tracing with React

React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".

With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.

eldh

import * as React from "react";
import { useMousePosition } from "~/hooks/useMousePosition";

/** Component to cover the area between the mouse cursor and the sub-menu, to allow moving cursor to lower parts of sub-menu without the sub-menu disappearing. */
export function MouseSafeArea(props: { parentRef: React.RefObject<HTMLDivElement> }) {
  const { x = 0, y = 0, height: h = 0, width: w = 0 } = props.parentRef.current?.getBoundingClientRect() || {};
  const [mouseX, mouseY] = useMousePosition();
  const positions = { x, y, h, w, mouseX, mouseY };
  return (
    <div

sindresorhus

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:

1. 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.
2. If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
3. Stay on the existing version of the package until you can move to ESM.