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

@onodocs/editor

v0.5.6

Published

OnoDocs browser Word editor, forms, review and application workflows.

Readme

OnoDocs Editor

@onodocs/editor provides the browser editor, template and form authoring, review controls, application sessions and collaborative editing UI. It uses the public document operations in @onodocs/sdk and presentation in @onodocs/canvas. Installing Editor installs matching SDK and Canvas versions. OnoDocs-authored Editor code is licensed under MIT, including its UI, application sessions, forms, templates and collaboration client. You may modify and redistribute that code, including in commercial products, while preserving the MIT notice and applicable third-party notices. SDK and Canvas remain separately commercially licensed; their production use requires covered application scope. Editor has no separate entitlement or purchase.

The editor source and runnable examples are maintained in the public OnoDocs repository. MIT permission for the editor does not grant production or redistribution rights in its SDK and Canvas dependencies.

npm install @onodocs/editor
import { createEditor } from "@onodocs/editor";

const editor = createEditor({ container, document: { licenseKey } });
await editor.open(bytes);
const saved = await editor.save();
editor.dispose();

Use createTemplateEditor from the same entry for template authoring. @onodocs/editor/application provides autosave, recovery and host lifecycle. @onodocs/editor/forms provides controlled form filling and the form designer. @onodocs/editor/collaboration provides the collaborative editor, browser recovery and transport client. The host supplies authentication, persistence and collaboration service endpoints.

createFormDesigner includes a Forms tab for adding fields and opening their sidebar settings. Supply onPreview(designer) and onExportProject(designer) to expose your host's preview and project-export actions there. Both callbacks can call designer.save() to obtain matching Word bytes and field rules. Set ribbon: false to keep only the standard editor tabs and field sidebar. The complete document-forms example connects these actions to its existing fill and ZIP export workflows.

Runnable editor and workflow examples live in onodocs/onodocs. The npm package contains the editor library. See the SDK guide and the included workflow guides for supported document operations and limitations.

Migration from 0.4

| Previous import | Current import | | --- | --- | | @onodocs/sdk/editor | @onodocs/editor | | @onodocs/sdk/application | @onodocs/editor/application | | @onodocs/sdk/forms/browser | @onodocs/editor/forms | | @onodocs/sdk/collaboration/browser | @onodocs/editor/collaboration |

Function names and supported behavior remain the same. The previous SDK entry points are removed. Document operations stay in @onodocs/sdk, /browser and /server. Form definitions, answers and validation stay in @onodocs/sdk/forms; the collaboration service and protocol stay in @onodocs/sdk/collaboration. HTTP integration stays in @onodocs/sdk/http. Canvas imports remain unchanged.

For backend rendering, install @onodocs/sdk playwright-core and provide a Chromium-family browser. Playwright is an optional SDK peer dependency; browser and data-only installations do not need it. The server adapter, HTTP service, form data operations and collaboration service have independent entry points and do not load the editor UI.

One named-application license covers commercial SDK and Canvas use, including the application's backend and self-hosted collaboration. Finished editors for end users are included. Editor source remains available under MIT. See application scope, output rights and redistribution terms.