npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@univerjs-pro/edit-history

v1.0.3

Published

Product-agnostic edit history services for Univer Pro.

Readme

@univerjs-pro/edit-history

npm version license downloads

Product-agnostic version history services for Univer Pro.

Package Overview

| Package | UMD global | CSS | Locales | Facade entry | | --- | --- | :---: | :---: | :---: | | @univerjs-pro/edit-history | UniverProEditHistory | No | No | Yes |

Installation

pnpm add @univerjs-pro/edit-history
# or
npm install @univerjs-pro/edit-history

Keep all @univerjs/* and @univerjs-pro/* packages on the same version.

Usage

Semantic comparison

createUnitComparisonEngine() compares two fully materialized UnitData snapshots without constructing a Univer instance. Register only the product adapters your application uses:

import { DocsUnitComparisonAdapter } from '@univerjs-pro/docs-history';
import {
    createUnitComparisonEngine,
    UnitComparisonDetailLevel,
    UnitComparisonFidelity,
} from '@univerjs-pro/edit-history';
import { UniverInstanceType } from '@univerjs/core';

const comparison = createUnitComparisonEngine([new DocsUnitComparisonAdapter()]);
const result = comparison.compare({
    comparisonId: 'review-42',
    unitId: 'doc-1',
    type: UniverInstanceType.UNIVER_DOC,
    fidelity: UnitComparisonFidelity.SNAPSHOT,
    leftData: {
        body: { dataStream: 'Review\r\n', paragraphs: [{ paragraphId: 'p1', startIndex: 6 }] },
    },
    rightData: {
        body: { dataStream: 'Publish\r\n', paragraphs: [{ paragraphId: 'p1', startIndex: 7 }] },
    },
});

console.log(result.summary, result.items);

Call comparison.prepare() once and comparison.query() repeatedly when a UI needs filtering or pagination. The prepared value retains comparison metadata and semantic results, not the two complete input snapshots.

For products with independently navigable views, result.scopes contains the changed worksheets, slides, Base tables, or Board pages in stable visual order. Every scoped item carries the same reference, so an agent or UI can build tabs and request one view without interpreting product snapshots:

const prepared = comparison.prepare(input);
const overview = comparison.query(prepared, { detail: UnitComparisonDetailLevel.SUMMARY });
const selectedScope = overview.scopes[0];
const selectedView = selectedScope === undefined
    ? overview
    : comparison.query(prepared, { scope: selectedScope, limit: 1000 });

console.log(selectedView.items);

In a Univer application, import @univerjs-pro/edit-history/facade, register the relevant product History plugin, and call univerAPI.compareUnitData() or univerAPI.prepareUnitComparison().

Integration Notes

  • Keep all @univerjs/* and @univerjs-pro/* packages on the same version.
  • Import @univerjs-pro/edit-history/facade when using the package through Univer Facade APIs.

Resources