github.com/brisa-build/diff-dom-streaming @0.6.6

  <img src="https://github.com/aralroca/diff-dom-streaming/assets/13313058/6d544ef2-651e-4907-a246-abc6c859ab5c" width="128">



    <h1 align="center">Diff DOM Streaming</h1>

The Diff DOM (Document Object Model) algorithm is used to compare two versions of the DOM, such as before and after an update on a web page. It aims to efficiently identify the changes between both DOMs, minimizing the number of manipulations required to update the user interface.

The Diff DOM Streaming library extends the traditional Diff DOM algorithm by introducing support for comparing a DOM node with a stream. This enables the library to process the changes incrementally as they occur during the diff process.

For more info, read this:

• HTML Streaming Over the Wire | A Deep Dive.
• SPA-like Navigation Preserving Web Component State

Getting started

NPM

Install:

bun install diff-dom-streaming

Then import it:

import diff from "diff-dom-streaming";

JSR

Install:

bunx jsr add @aralroca/diff-dom-streaming

Then import it:

import diff from "@aralroca/diff-dom-streaming";

UNPKG

Just import it:

import diff from "https://unpkg.com/diff-dom-streaming@latest";

Using it

const res = await fetch(/* some url */);

// Diff between the current document and the stream:
await diff(document, res.body);

API

diff(oldNode: Node, stream: ReadableStream<Uint8Array>, options?: Options): Promise<void>

This function performs a diffing operation between the oldNode and the DOM tree from a stream. It applies the necessary changes to update the oldNode accordingly. An optional options that include:

type Options = {
  // calback to handle each new docoument node during the streaming
  // (default: undefined)
  onNextNode?: NextNodeCallback;
  // update the DOM using document.startViewTransition (default: false)
  transition?: boolean;
  // callback to ignore nodes (default: undefined)
  shouldIgnoreNode?: (node: Node | null) => boolean;
};

Lists and key attribute

Keys help to identify which items have changed, are added, or are removed. Keys should be given to the elements inside the array to give the elements a stable identity:

```jsx 3 const numbers = [1, 2, 3, 4, 5]; const listItems = numbers.map((number) => (

{number}

));

_(Example with JSX)_

The `diff-dom-streaming` library takes into account the `key` attribute for these cases, if it does not exist, then see if they have `id`.

## Transitions between pages (View Transition API)

You can activate the View Transition API updating the DOM with this property:

```diff
await diff(document, res.body, {
+ transition: true
})

[!TIP]

To access the transition with JavaScript/TypeScript you can access the global property window.lastDiffTransition

Incremental vs full transition

Many times it will make more sense to use a complete transition instead of incremental, especially if we do not use suspense and we want a single transition at once instead of several, in this case, instead of using the configuration, we can use the View Transition API directly:

+ document.startViewTransition(async () => {
await diff(document, res.body, {
-  transition: true,
});
+});

Strong Opinion on BODY Tag Attributes during Diffing

Our library has a strong opinion regarding the handling of the BODY tag attributes during the HTML diffing process. This approach is designed to provide greater flexibility and control over runtime modifications, such as themes, fonts, and other display properties that are managed through BODY tag attributes.

During the diffing process, all content within the HTML is typically updated to reflect the latest changes. However, we recognize that certain attributes of the BODY tag, like class and custom data-attributes, are often modified at runtime to control the presentation of the content. To avoid overwriting these runtime changes, our library's diffing algorithm specifically excludes these attributes from being updated.

Key Points

• Preservation of Attributes: Attributes of the BODY tag (e.g., class, data-attributes) are preserved and not overwritten during the diffing process.
• Consistent Display: This ensures that runtime modifications, such as theme changes or other display-related adjustments, remain intact across navigations and updates.
• Enhanced Customization: Users can rely on the BODY tag attributes to manage display properties without concern for them being reset during content updates.

Example

Consider the following scenario where the initial HTML and updated HTML are as follows:

Initial HTML

<body class="light" data-theme="default">


Content A


</body>

Updated HTML

After a navigation or content update, the new HTML may look like this:

<body class="dark" data-theme="night">


Content B


</body>

Result After Diffing

After the diffing process, the resulting HTML will be as follows:

<body class="light" data-theme="default">


Content B


</body>

Examples

In the repo we have examples for you to try.

Locally

There are some examples:

• Run bun run example:boxes
• Run bun run examples:spa-like

Stackblitz

You can run the boxes demo with Vanillajs here.

Acknowledgments

The Diff DOM Algorithm with HTML Streaming is inspired by the set-dom library by @dylan_piercey and a technique for parsing streams pioneered by @jaffathecake.

Contributing

See Contributing Guide and please follow our Code of Conduct.

License

MIT