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

@nonoim/editor-core

v0.5.1

Published

Framework-independent Markdown, recovery backup and image upload contracts for nonoMark.

Readme

@nonoim/editor-core

Framework-independent Markdown compatibility checks, editor recovery backups and image upload contracts for nonoMark.

Recovery backups

createEditorBackup stores a JSON-serializable editor payload under one stable backupKey. It does not know about Vue, React, PocketBase, authentication or a particular form shape.

import { createEditorBackup } from '@nonoim/editor-core/backup';

const backup = createEditorBackup({
  backupKey: 'admin-42:posts:post-123',
  debounceMs: 800,
  onStatus: ({ status }) => console.log(status),
  onError: ({ operation, error }) => console.error(operation, error),
});

const pending = await backup.discover();
if (pending) {
  // Let the host UI offer: restore() or discard().
}

backup.schedule({
  title: form.title,
  summary: form.summary,
  markdown: form.markdown,
  category: form.category,
  seo: form.seo,
});

const restoredForm = await backup.restore();

await saveForm();
await backup.clear();

The default adapter is browser localStorage. Pass any getItem / setItem / removeItem adapter to use another storage mechanism. flush() immediately persists a scheduled payload, while destroy() cancels a pending timer without deleting an existing backup.

Backups contain JSON data only. File, Blob, DOM nodes and other non-JSON values must remain in the host application. The host owns recovery prompts, applying restored data and deciding when a formal save has succeeded.

Remote image imports

The core exports findRemoteImageReferences, replaceRemoteImageReferences, and importRemoteImagesFromContent. They detect http/https images in one Markdown or HTML fragment, skip code and local/data URLs, and replace only results returned by a host callback.

const result = await importRemoteImagesFromContent(markdown, async (images, { signal }) => {
  return hostImport(images, { signal });
}, context);

Return each successful asset with its input reference id. A missing result preserves the original URL. This package does not download images, authenticate requests, or depend on a storage provider.