# Custom Cursor

> Inside its zone the pointer becomes a dot with a soft lag, and a pill that says what a click will do over each item. No GSAP.

Cursor · cursor, hover, pointer, image · HTML, CSS, vanilla JS · no dependencies · updated 2026-10-16
Demo: https://kodza.dev/components/hover-custom-cursor/

## Files

The code below, served as files: byte for byte what the Kodza site copies (the CSS includes its theme guard).

- [`kodza-hover-custom-cursor.css`](https://kodza.dev/registry/hover-custom-cursor/kodza-hover-custom-cursor.css) · 5.5 KB
- [`kodza-hover-custom-cursor.js`](https://kodza.dev/registry/hover-custom-cursor/kodza-hover-custom-cursor.js) · 4.0 KB
- [`kodza-hover-custom-cursor.html`](https://kodza.dev/registry/hover-custom-cursor/kodza-hover-custom-cursor.html) · 0.7 KB · the markup, to adapt and paste into your page

**Can you run shell commands? Download the CSS and the JS, don't retype them.** Retyping costs thousands of tokens and can drop or change lines of the CSS. Put the files where your stack expects them (Use it says where: change the `-o` paths):

```bash
curl -fsSL --create-dirs -o kodza/kodza-hover-custom-cursor.css https://kodza.dev/registry/hover-custom-cursor/kodza-hover-custom-cursor.css
curl -fsSL --create-dirs -o kodza/kodza-hover-custom-cursor.js https://kodza.dev/registry/hover-custom-cursor/kodza-hover-custom-cursor.js
```

Then load the files from your page as Use it shows, instead of pasting the content. The HTML is the part you adapt (text, links, modifiers): paste it from the Code section. Copy the CSS and the JS from the Code section only if you can't run commands, exactly as they are. (Windows PowerShell: `curl.exe`.)

## API

- Root: `.kodza-cursor-zone`
- Variables (set them on the root element itself: it declares its own defaults):
  - `--kz-cursor-bg: #0a0a0a`
  - `--kz-cursor-fg: #ffffff`
  - `--kz-cursor-dot: 10px`
  - `--kz-cursor-ratio: 4 / 5`
  - `--kz-cursor-radius: 4px`
  - `--kz-cursor-placeholder: rgba(10, 10, 10, 0.06)`
- Attributes:
  - `data-cursor` (e.g. `View`, `Open`, `Ship it`)
- Lifecycle: `kodza:init` / `kodza:destroy` on `document`, with `{ detail: { root } }` to target a container.

## Dark mode

The values Kodza uses on a dark background (`#0a0a0a`). For a page that follows the system theme, add them after the component's CSS:

```css
@media (prefers-color-scheme: dark) {
  .kodza-cursor-zone {
    --kz-cursor-bg: #ffffff;
    --kz-cursor-fg: #0a0a0a;
    --kz-cursor-placeholder: rgba(255, 255, 255, 0.06);
  }
}
```

A site with its own theme switch puts the same rules under its dark selector instead (`[data-theme="dark"] .kodza-cursor-zone { … }`); a single dark section, under that section's class.

Its images have dark versions next to them (`kz-block-1400.webp` → `kz-block-dark-1400.webp`). To swap them on a dark page: `<picture><source media="(prefers-color-scheme: dark)" srcset="…-dark-….webp"><img …></picture>`.

## Use it

### Plain HTML page

- CSS: `kodza/kodza-hover-custom-cursor.css` next to the page (the Files commands as they are), linked in `<head>`: `<link rel="stylesheet" href="kodza/kodza-hover-custom-cursor.css">`. Without a shell, paste it in a `<style>` in `<head>` instead. It only touches `kodza-` classes.
- HTML: where the component goes. Paste it as many times as you need: instances never interfere.
- JS: `kodza/kodza-hover-custom-cursor.js`, loaded with `<script src="kodza/kodza-hover-custom-cursor.js" defer></script>` in `<head>`. Without a shell, paste it in a `<script>` before `</body>` (or in `<head>`: it waits for the page). One copy per page, whatever the number of instances.
- Restyle with the `--kz-…` variables, set on the component's root element itself (the root declares its own defaults, so a value on an ancestor is ignored), and with the modifiers / attributes listed under API.
- Font: it takes the page's own. The Kodza look is Geist: `<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Geist:wght@400;500;600;700&family=Geist+Mono:wght@400;500&display=swap">`.
- Content added later (AJAX navigation, a SPA route, a builder preview): start it with `document.dispatchEvent(new CustomEvent('kodza:init', { detail: { root: container } }))`; before removing it, the same call with `'kodza:destroy'` stops it and puts the original markup back.

### Claude artifact (claude.ai)

- Paste the CSS in a `<style>` and the JS in a `<script>` at the end, in the artifact itself: it loads stylesheets only from Google Fonts and scripts only from a few CDNs, so no `<link>` or `<script src>` to Kodza.
- Writing the artifact file with a shell? Insert the downloaded files (Files) with a command instead of retyping them: a line `KODZA-CSS` alone inside the `<style>`, `KODZA-JS` inside the `<script>`, then `sed -e '/^KODZA-CSS$/{r kodza/kodza-hover-custom-cursor.css' -e 'd' -e '}' -e '/^KODZA-JS$/{r kodza/kodza-hover-custom-cursor.js' -e 'd' -e '}' page.html > artifact.html`.
- Font: load Geist from Google Fonts (allowed): `<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Geist:wght@400;500;600;700&family=Geist+Mono:wght@400;500&display=swap">`.
- Images: the artifact blocks every other host, `kodza.dev` included, without an error. Embed each one as a `data:` URI, with a command if you can run one (`curl -s <url> | base64`; the 1400 px files weigh 10 to 30 KB), never by typing base64 out. If you can't run commands, keep the `<img>` with its `width` and `height`, and tell the user the picture stays blank inside the artifact.
- Dark mode: the viewer sets `data-theme="dark"` or `"light"` on `<html>`, or nothing when it follows the system. Write the Dark mode rules twice: inside `@media (prefers-color-scheme: dark)` with `:root:not([data-theme="light"])` in front of each selector, and with `:root[data-theme="dark"]` in front of each selector.

### WordPress

- HTML: a **Custom HTML** block (or a pattern / template part). WordPress keeps this markup as it is only for users allowed to post unfiltered HTML (Administrators; Super Admins on multisite): for anyone else it strips tags such as `<svg>`, `<input>` or `<dialog>`, so add it from the theme (a pattern or template part) instead.
- CSS and JS: the downloaded files go in the theme, under `wp-content/themes/<your-theme>/kodza/` (the child theme if there is one), enqueued from its functions.php (or a code-snippets plugin):
  ```php
  add_action('wp_enqueue_scripts', function () {
    $dir = get_stylesheet_directory() . '/kodza/';
    $uri = get_stylesheet_directory_uri() . '/kodza/';
    wp_enqueue_style('kodza-hover-custom-cursor', $uri . 'kodza-hover-custom-cursor.css', [], filemtime($dir . 'kodza-hover-custom-cursor.css'));
    wp_enqueue_script('kodza-hover-custom-cursor', $uri . 'kodza-hover-custom-cursor.js', [], filemtime($dir . 'kodza-hover-custom-cursor.js'), true);
  });
  ```
  Scoped to `kodza-` classes, the CSS never touches the theme. One copy of the JS, whatever the number of blocks.
- No access to the theme files? The CSS can also go, as it is, in **Appearance → Customize → Additional CSS** (classic theme) or **Styles → Additional CSS** in the Site Editor (block theme).
- Theme with AJAX page transitions: fire `kodza:init` on the new content after each swap (and `kodza:destroy` on the old one).
- Performance plugin (WP Rocket, LiteSpeed Cache, Perfmatters…) with **Delay JavaScript execution** turned on: add `kodza` to the scripts it must not delay. Otherwise the component waits for the visitor's first scroll, tap or mouse move, and that first click can be lost.
- Colours: it takes the colour of the text around it (or keeps its own monochrome): nothing to point at the theme.
- WordPress turns straight quotes and `--` into typographic ones in the text of a Custom HTML block (not inside `<code>` or `<pre>`).

#### With Elementor

- HTML: an **HTML** widget (Elementor shows it to administrators only). It keeps the code exactly as pasted, straight quotes included.
- CSS and JS: as above. Elementor's Site Settings → Theme Style styles every button, field, link and image of the page, components included; the theme guard at the end of the CSS keeps the component's buttons, fields and link colours as they are.
- The Elementor editor redraws each widget after the page has loaded: without the script below, the component stays still in the editor preview (the published page works). Add it once per site, in the footer like the component's script (`kodza/elementor-editor.js`, or a code-snippets plugin):

```js
// Kodza in the Elementor editor: the editor redraws each HTML widget after the page has loaded.
// Start Kodza in what it draws, stop it in what it replaces or removes. Once per site.
window.addEventListener('elementor/frontend/init', () => {
  if (!elementorFrontend.isEditMode()) return;
  class KodzaWidget extends elementorModules.frontend.handlers.Base {
    onInit() {
      super.onInit();
      this.kodza = [...this.$element[0].children];
      document.dispatchEvent(new CustomEvent('kodza:init', { detail: { root: this.$element[0] } }));
    }
    onDestroy() {
      super.onDestroy();
      this.kodza.forEach((root) => document.dispatchEvent(new CustomEvent('kodza:destroy', { detail: { root } })));
    }
  }
  elementorFrontend.elementsHandler.attachHandler('html', KodzaWidget);
});
```

- No child theme: everything can go in the HTML widget instead, `<style>` with the CSS, the HTML, then `<script>` with the JS. It works on the page and in the editor without the script above.

### Shopify

- Files: `assets/kodza-hover-custom-cursor.css` and `assets/kodza-hover-custom-cursor.js` (the Files commands with `-o assets/…`).
- In the section: `{{ 'kodza-hover-custom-cursor.css' | asset_url | stylesheet_tag }}` and `<script src="{{ 'kodza-hover-custom-cursor.js' | asset_url }}" defer></script>`, then the HTML.
- The theme editor re-renders sections: restart them with
  `document.addEventListener('shopify:section:load', (e) => document.dispatchEvent(new CustomEvent('kodza:init', { detail: { root: e.target } })));`
  and the same with `shopify:section:unload` → `kodza:destroy`.

### React / Next.js

- Files, side by side (e.g. in `components/kodza/`): `CustomCursor.tsx` (below), the CSS block under Code saved as `hover-custom-cursor.css` and the JS block as `hover-custom-cursor.js`, both as they are. The HTML block is already inside the component: skip it.
- Use it: `import { CustomCursor } from '@/components/kodza/CustomCursor';` then `<CustomCursor />`. Props: `vars` (the `--kz-…` variables listed under API, e.g. `vars={{ '--kz-cursor-bg': … }}`), `className`, `style` and the other props of its `<div>` (`onClick`, `aria-…`).
- Next.js App Router: it is a Client Component already (`'use client'`). Pages Router: Next.js takes global CSS only in `pages/_app`, so move the `import './hover-custom-cursor.css'` line there.
- Safe under StrictMode, client-side navigation and prop changes: when a prop changes, the `key` gives React a fresh element, `kodza:destroy` stops the script on the old one and `kodza:init` starts it on the new one.

```tsx
'use client';
// Kodza — Custom Cursor, for React. From https://kodza.dev/components/hover-custom-cursor/
// Kodza License: free to use, client work included. Not to resell or redistribute, ported or not: https://kodza.dev/docs/#print-license
// Next to this file: hover-custom-cursor.css and hover-custom-cursor.js, the component's CSS and JS from Kodza, as they are.
// Yours to edit: the markup is plain JSX below.
// The script changes this markup once React has rendered it (it adds layers, splits text, moves
// nodes), so React must not patch it afterwards. When a prop changes, the key gives React a fresh
// element: kodza:destroy stops the script on the old one, kodza:init starts it on the new one.
import { useRef, useEffect, type ComponentPropsWithoutRef, type ComponentRef, type CSSProperties } from 'react';
import './hover-custom-cursor.css';

export type CustomCursorProps = Omit<ComponentPropsWithoutRef<'div'>, "children" | "vars"> & {
  /** Settings, as CSS variables on the root */
  vars?: {
    /** default: #0a0a0a */
    "--kz-cursor-bg"?: string | number;
    /** default: #ffffff */
    "--kz-cursor-fg"?: string | number;
    /** default: 10px */
    "--kz-cursor-dot"?: string | number;
    /** default: 4 / 5 */
    "--kz-cursor-ratio"?: string | number;
    /** default: 4px */
    "--kz-cursor-radius"?: string | number;
    /** default: rgba(10, 10, 10, 0.06) */
    "--kz-cursor-placeholder"?: string | number;
  };
  className?: string;
};

export function CustomCursor({ vars, className, style, ...rest }: CustomCursorProps) {
  const ref = useRef<ComponentRef<'div'>>(null);
  const classes = ["kodza-cursor-zone", className].filter(Boolean).join(' ');
  // Everything the markup is made of: when it changes, React gets a fresh element (see the top)
  const key = JSON.stringify([classes, vars, style, rest]);

  // Starts the script on this element once React has rendered it, stops it when it goes
  useEffect(() => {
    const root = ref.current;
    let live = true;
    // @ts-ignore: a plain script, no types to find
    import('./hover-custom-cursor.js').then(() => {
      if (live) document.dispatchEvent(new CustomEvent('kodza:init', { detail: { root } }));
    });
    return () => {
      live = false;
      document.dispatchEvent(new CustomEvent('kodza:destroy', { detail: { root } }));
    };
  }, [key]);

  return (
    <div key={key} {...rest} className={classes} style={{ ...vars, ...style } as CSSProperties} ref={ref}>
      <a className="kodza-cursor-zone__item" href="#" data-cursor="View">
        <img src="https://kodza.dev/media/kz-block-1400.webp" alt="A tall concrete slab standing alone, its long shadow stretching toward the viewer" loading="lazy" />
      </a>
      {' '}
      <a className="kodza-cursor-zone__item" href="#" data-cursor="Open">
        <img src="https://kodza.dev/media/kz-columns-1400.webp" alt="A row of square concrete pillars under a flat roof, casting striped shadows" loading="lazy" />
      </a>
      {' '}
      <a className="kodza-cursor-zone__item" href="#" data-cursor="Ship it">
        <img src="https://kodza.dev/media/kz-float-1400.webp" alt="A concrete block hovering above the ground, over its own shadow" loading="lazy" />
      </a>
    </div>
  );
}
```

## Code

```html
<div class="kodza-cursor-zone">
  <a class="kodza-cursor-zone__item" href="#" data-cursor="View">
    <img src="https://kodza.dev/media/kz-block-1400.webp" alt="A tall concrete slab standing alone, its long shadow stretching toward the viewer" loading="lazy" />
  </a>
  <a class="kodza-cursor-zone__item" href="#" data-cursor="Open">
    <img src="https://kodza.dev/media/kz-columns-1400.webp" alt="A row of square concrete pillars under a flat roof, casting striped shadows" loading="lazy" />
  </a>
  <a class="kodza-cursor-zone__item" href="#" data-cursor="Ship it">
    <img src="https://kodza.dev/media/kz-float-1400.webp" alt="A concrete block hovering above the ground, over its own shadow" loading="lazy" />
  </a>
</div>
```

```css
/* Kodza License: free to use, client work included. Not to resell or redistribute, ported or not: https://kodza.dev/docs/#print-license */
/* Kodza — Custom Cursor
   Inside its zone the pointer becomes a small dot that follows with a soft lag; over an
   item it grows into a pill that says what a click will do (data-cursor="…").
   Hidden on touch screens, where there is no pointer to follow.
   Everything is tuned with the --kz-cursor-* variables. */
.kodza-cursor-zone {
  --kz-cursor-bg: #0a0a0a;
  --kz-cursor-fg: #ffffff;
  --kz-cursor-dot: 10px;
  --kz-cursor-ratio: 4 / 5;
  --kz-cursor-radius: 4px;
  --kz-cursor-placeholder: rgba(10, 10, 10, 0.06);

  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(160px, 1fr));
  gap: clamp(14px, 2vw, 24px);
}

.kodza-cursor-zone__item {
  display: block;
  aspect-ratio: var(--kz-cursor-ratio);
  overflow: hidden;
  border-radius: var(--kz-cursor-radius);
  background: var(--kz-cursor-placeholder);
}

.kodza-cursor-zone__item img {
  display: block;
  width: 100%;
  height: 100%;
  object-fit: cover;
}

.kodza-cursor-zone__item:focus-visible {
  outline: 2px solid currentColor;
  outline-offset: 4px;
}

/* The pointer is replaced only where the custom cursor can follow it */
@media (hover: hover) and (pointer: fine) {
  .kodza-cursor-zone.is-ready,
  .kodza-cursor-zone.is-ready * {
    cursor: none;
  }
}

/* The cursor itself (created by the script): a dot, and a pill for the labels.
   Only transform and opacity move, so it costs nothing to the page layout. */
.kodza-cursor-zone__cursor {
  position: fixed;
  top: 0;
  left: 0;
  z-index: 50;
  width: 0;
  height: 0;
  pointer-events: none;
  opacity: 0;
  transition: opacity 0.25s ease;
}

.kodza-cursor-zone__cursor.is-visible {
  opacity: 1;
}

.kodza-cursor-zone__dot,
.kodza-cursor-zone__pill {
  position: absolute;
  top: 0;
  left: 0;
  border-radius: 999px;
  background: var(--kz-cursor-bg);
  translate: -50% -50%;
  transition: transform 0.45s cubic-bezier(0.22, 1, 0.36, 1), opacity 0.3s ease;
}

.kodza-cursor-zone__dot {
  width: var(--kz-cursor-dot);
  height: var(--kz-cursor-dot);
}

.kodza-cursor-zone__pill {
  display: grid;
  place-items: center;
  height: 40px;
  padding: 0 16px;
  color: var(--kz-cursor-fg);
  font-size: 14px;
  font-weight: 500;
  white-space: nowrap;
  opacity: 0;
  transform: scale(0.2);
}

.kodza-cursor-zone__cursor.is-label .kodza-cursor-zone__dot {
  opacity: 0;
  transform: scale(0.4);
}

.kodza-cursor-zone__cursor.is-label .kodza-cursor-zone__pill {
  opacity: 1;
  transform: none;
}

@media (prefers-reduced-motion: reduce) {
  .kodza-cursor-zone__cursor,
  .kodza-cursor-zone__dot,
  .kodza-cursor-zone__pill {
    transition-duration: 0.01ms !important;
  }
}

/* Theming example — on a dark background:
.dark-section .kodza-cursor-zone {
  --kz-cursor-bg: #ffffff;
  --kz-cursor-fg: #0a0a0a;
}
*/

/* kodza-guard d13c444ef902 — generated by Kodza, do not edit.
   Theme guard: keeps a site's own CSS (WordPress themes, Bootstrap, CSS resets…) off this
   component. :not(#_) is always true and weighs as much as an id, so these lines win over
   theme rules made of classes and tags. Customise the component through its --kz-* variables. */

/* What the browser gives, where the component sets it only in some states: at the lowest weight, so its own rules below put it back */

:where(.kodza-cursor-zone__item):not(#_) {
  outline: revert;
  outline-offset: revert;
}

/* What the browser gives, on everything the component leaves to it */

.kodza-cursor-zone:not(#_),
.kodza-cursor-zone__cursor:not(#_),
.kodza-cursor-zone__dot:not(#_),
.kodza-cursor-zone__pill:not(#_) {
  box-sizing: revert;
}

.kodza-cursor-zone__item:not(#_) {
  border: revert;
  margin: revert;
  padding: revert;
  text-decoration: revert;
  transition: revert;
  list-style: revert;
  box-sizing: revert;
  float: revert;
  position: revert;
  box-shadow: revert;
  appearance: revert;
  max-width: revert;
  max-height: revert;
  color: revert;
  font-family: revert;
  font-size: revert;
  font-weight: revert;
  font-style: revert;
  line-height: revert;
  letter-spacing: revert;
  text-transform: revert;
  text-underline-offset: revert;
  text-align: revert;
  text-indent: revert;
  text-shadow: revert;
  vertical-align: revert;
}

.kodza-cursor-zone__item img:where(:not([class*="kodza-"])):not(#_) {
  border: revert;
  margin: revert;
  padding: revert;
  border-radius: revert;
  outline: revert;
  text-decoration: revert;
  transition: revert;
  list-style: revert;
  box-sizing: revert;
  float: revert;
  position: revert;
  background-color: revert;
  background-image: revert;
  box-shadow: revert;
  outline-offset: revert;
  appearance: revert;
  max-width: revert;
  max-height: revert;
  color: revert;
  font-family: revert;
  font-size: revert;
  font-weight: revert;
  font-style: revert;
  line-height: revert;
  letter-spacing: revert;
  text-transform: revert;
  text-underline-offset: revert;
  text-align: revert;
  text-indent: revert;
  text-shadow: revert;
  vertical-align: revert;
}

/* The component's own rules, one step stronger: real buttons and fields, what it sets on tags themes style (links, lists, headings, images…), and the root width (a theme may narrow it, never widen it) */

.kodza-cursor-zone__item:not(#_) {
  display: block;
  border-radius: var(--kz-cursor-radius);
  background: var(--kz-cursor-placeholder);
}

.kodza-cursor-zone__item img:not(#_) {
  display: block;
}

.kodza-cursor-zone__item:focus-visible:not(#_) {
  outline: 2px solid currentColor;
  outline-offset: 4px;
}
```

```js
// Kodza License: free to use, client work included. Not to resell or redistribute, ported or not: https://kodza.dev/docs/#print-license
// Kodza — Custom Cursor
// One cursor per zone. It follows the pointer with a soft lag (a little easing each
// frame, only while it moves), and shows the data-cursor label of the item under it.
// Touch screens and reduced motion keep the normal pointer, or a cursor without lag.
(() => {
  const SELECTOR = '.kodza-cursor-zone';
  if (!window.matchMedia('(hover: hover) and (pointer: fine)').matches) return;
  const reduceMotion = window.matchMedia('(prefers-reduced-motion: reduce)').matches;
  const FOLLOW = reduceMotion ? 1 : 0.2; // how much of the way it catches up each frame

  // One instance. Everything it starts is tied to `signal`, so kodza:destroy stops it all
  function mount(zone, signal) {
    const cursor = document.createElement('div');
    cursor.className = 'kodza-cursor-zone__cursor';
    cursor.setAttribute('aria-hidden', 'true');
    const dot = document.createElement('span');
    dot.className = 'kodza-cursor-zone__dot';
    const label = document.createElement('span');
    label.className = 'kodza-cursor-zone__pill';
    cursor.append(dot, label);
    zone.append(cursor);
    zone.classList.add('is-ready');

    const target = { x: 0, y: 0 };
    const pos = { x: 0, y: 0 };
    let frame = null;

    const render = () => {
      if (signal.aborted) return;
      pos.x += (target.x - pos.x) * FOLLOW;
      pos.y += (target.y - pos.y) * FOLLOW;
      cursor.style.transform = `translate3d(${pos.x}px, ${pos.y}px, 0)`;
      const still = Math.abs(target.x - pos.x) < 0.1 && Math.abs(target.y - pos.y) < 0.1;
      frame = still ? null : requestAnimationFrame(render);
    };

    zone.addEventListener('pointerenter', (event) => {
      // Appear right under the pointer, not sliding in from a corner
      target.x = pos.x = event.clientX;
      target.y = pos.y = event.clientY;
      render();
      cursor.classList.add('is-visible');
    }, { signal });
    zone.addEventListener('pointermove', (event) => {
      target.x = event.clientX;
      target.y = event.clientY;
      const item = event.target.closest('[data-cursor]');
      if (item) label.textContent = item.dataset.cursor;
      cursor.classList.toggle('is-label', Boolean(item));
      if (!frame) frame = requestAnimationFrame(render);
    }, { signal });
    zone.addEventListener('pointerleave', () => cursor.classList.remove('is-visible', 'is-label'), { signal });
  }

  // Kodza lifecycle, the same in every component: `kodza:init` starts the instances inside
  // event.detail.root (the whole page by default), `kodza:destroy` stops them and puts their
  // markup back. For themes and apps that swap content without a page load.
  const instances = new WeakMap();
  const find = (scope = document) => [scope, ...scope.querySelectorAll(SELECTOR)].filter((el) => el.matches?.(SELECTOR));
  const init = (scope) => find(scope).forEach((root) => {
    if (root.classList.contains('is-ready')) return; // already running, maybe from another copy of this script
    const controller = new AbortController();
    instances.set(root, { controller, html: root.innerHTML, attrs: [...root.attributes].map((a) => [a.name, a.value]) });
    mount(root, controller.signal);
    root.classList.add('is-ready');
  });
  const destroy = (scope) => find(scope).forEach((root) => {
    const instance = instances.get(root);
    if (!instance) return;
    instances.delete(root);
    instance.controller.abort();
    [...root.attributes].forEach((a) => root.removeAttribute(a.name));
    instance.attrs.forEach(([name, value]) => root.setAttribute(name, value));
    root.innerHTML = instance.html;
  });
  document.addEventListener('kodza:init', (event) => init(event.detail?.root));
  document.addEventListener('kodza:destroy', (event) => destroy(event.detail?.root));
  init();
  // Loaded in <head>, the script runs before the markup exists: once more when it is parsed
  if (document.readyState === 'loading') document.addEventListener('DOMContentLoaded', () => init(), { once: true });
})();
```

Free to use, from Kodza (https://kodza.dev).