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

@nextmoe/edit-ui-core

v0.2.0

Published

NextMoe edit-ui framework-free core — the wire/schema types of the schema-driven edit surface plus the pure diff, formatting and badge helpers. No Vue, no DOM framework.

Readme

@nextmoe/edit-ui-core

Framework-free core of the NextMoe edit-ui family: the wire/schema types of the schema-driven edit surface, plus the pure helpers the Vue layer renders with.

No Vue, no DOM framework — diff is the only runtime dependency, so a server or a CLI can import the same diff and formatting logic the UI uses.

pnpm add @nextmoe/edit-ui-core

What is in here

TypesEditSchemaField, EditControl, EditSelectOption, EditObjectColumn, EditContextItem, EditFieldConfig, EditFieldConfigMap, EditProposal, EditAmendment, EditRevision, EditUser, ImageDiffEntry.

Value helpersstableStringify, editValueEqual, cloneEditValue, formatEditValue, formatEditItem, diffItems.

Control resolutionresolveControl(field, config) picks the control for a schema field; EDIT_CONTROLS is the list of controls this version knows and isEditControl(value) is the forward-compatibility guard the Vue layer uses to degrade an unknown control to a read-only display.

Text diffdiffTextSegments, diffTextStats, isTextDiffElidable, elideTextDiff, TEXT_DIFF_ELIDE_OVER. CJK is segmented on word boundaries via Intl.Segmenter when the runtime has it.

BadgesproposalStatusBadge, revisionActionBadge.

The generic component slot

EditFieldConfig carries a component? escape hatch for a site-supplied custom field renderer. That is a Vue component — but typing it as one would put vue in this package's dependency closure, which is exactly what this package must not have. So the type is generic (EditFieldConfig<TComponent = unknown>) and @nextmoe/edit-ui-vue re-exports the specialisation EditFieldConfig<Component>. Use the vue package's type in a Vue app.

License

AGPL-3.0-only.