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

@kerebron/legacy-compat

v0.7.6

Published

Packages from NPM can be directly accessed using https://cdn.jsdelivr.net.

Readme

Compatibility layer for loading directly from browsers and old bundlers

Using Kerebron directly from CDN.

Packages from NPM can be directly accessed using https://cdn.jsdelivr.net.

This package has all editor modules combined and uploaded to CDN.

Exported methods are in ./mod.ts

Wasm assets from package @kerebron/wasm can be accessed from path:

https://cdn.jsdelivr.net/npm/@kerebron/wasm@latest/assets (no trailing slash to avoid 400 error).

Usage:

<button id="loadOdt">LOAD ODT</button>
<div id="editor"></div>
<style>
    @import "https://cdn.jsdelivr.net/npm/@kerebron/legacy-compat@latest/dist/kerebron.css";
/* For light only mode
    @import "https://cdn.jsdelivr.net/npm/@kerebron/legacy-compat@latest/dist/kerebron-light.css";
*/
</style>
<script type="module" defer>
    import * as Kerebron from "https://cdn.jsdelivr.net/npm/@kerebron/legacy-compat@latest/dist/kerebron.js";
    const { CoreEditor, AdvancedEditorKit, createAssetLoad } = Kerebron;

    const editor = CoreEditor.create({
        uri: "test.odt",
        assetLoad: createAssetLoad('https://cdn.jsdelivr.net/npm/@kerebron/wasm@latest/assets'),
        element: document.getElementById("editor"),
        editorKits: [new AdvancedEditorKit()],
    });

    document
        .getElementById("loadOdt")
        .addEventListener("click", async () => {
            const input = document.createElement("input");
            input.type = "file";
            input.addEventListener("change", async (e) => {
                const file = e.target.files[0];
                console.log("Selected file:", file);
                await editor.loadDocument(
                    file.type,
                    new Uint8Array(await file.arrayBuffer()),
                );
            });
            input.click();
            return true;
        });
</script>

Using Kerebron directly from old bundlers which do not undestand export paths.

<script type="module" defer>
    import * as Kerebron from "@kerebron/legacy-compat";
    const { CoreEditor, AdvancedEditorKit, createAssetLoad } = Kerebron;

    const editor = CoreEditor.create({
        uri: "test.odt",
        assetLoad: createAssetLoad('/wasm'), // Serve @kerebron/wasm assets under this path
        element: document.getElementById("editor"),
        editorKits: [new AdvancedEditorKit()],
    });

    document
        .getElementById("loadOdt")
        .addEventListener("click", async () => {
            const input = document.createElement("input");
            input.type = "file";
            input.addEventListener("change", async (e) => {
                const file = e.target.files[0];
                console.log("Selected file:", file);
                await editor.loadDocument(
                    file.type,
                    new Uint8Array(await file.arrayBuffer()),
                );
            });
            input.click();
            return true;
        });
</script>

Development

Building

deno task -f legacy-compat build

Testing before npm publish

Use index-dev.html file to check if it's loading correctly. It is the same as example above except that istead of using npm it is using npm package from http://localhost:8000/dist

deno task -f legacy-compat serve
  1. Go to: http://localhost:8000/index-dev.html
  2. Check if wasm is working correctly. Eg. open .odt file.