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

@letterpress/svelte

v0.1.4

Published

An accessible, themeable Svelte 5 editor shell for Letterpress.

Readme

@letterpress/svelte

A Svelte 5 editor component built on CodeMirror and @letterpress/language. It owns editor lifecycle, controlled source updates, profile/schema/diagnostic reconfiguration, keyboard save/format commands, read-only state, focus, and accessibility. Props configure line numbers, folding and lint gutters, wrapping, and placeholder text. Matching, indentation, completion, and search are included in the standard editor setup. It does not call a backend or make publication decisions.

The bundled editor theme is a complete light/dark reference pair. Override its --letterpress-editor-* CSS properties or build a paired product theme with createLetterpressEditorTheme. Theme values may reference product CSS variables. Select the active palette with colorScheme; changing modes keeps the current document, selection, and undo history.

Letterpress creates the underlying CodeMirror theme and highlighting extensions internally, so local linked consumers do not exchange identity-sensitive extension objects. The extensions prop remains available for advanced peer-deduplicated hosts.

<script lang="ts">
  import { LetterpressEditor } from "@letterpress/svelte"

  let source = $state("<mjml><mj-body /></mjml>")
  const schema = { version: 1 as const, variables: {} }
</script>

<LetterpressEditor
  bind:source
  profile="email/mjml-liquid@1"
  {schema}
  colorScheme="light"
/>

The component does not own product layout. Place it in the host product's own container and map the paired theme to that product's semantic tokens. It emits no breakpoint, card, dashboard, task-navigation, approval or publication policy. Resize or rearrange the host around the same mounted editor when selection, focus and undo history must continue. A remount restores the controlled source/schema/diagnostic values but creates new CodeMirror selection and history state.

Hosts that edit a preprocessing language may set clientDiagnostics={false} and pass diagnostics from the backend after expansion. Grammar, highlighting, completion, formatting, and freshness-filtered server diagnostics remain enabled. Strict client diagnostics stay enabled by default.

Mod-s invokes onSave; Shift-Alt-f formats the current document and invokes onFormat. If formatting finishes after the document or profile changes, the result is discarded. A read-only editor does not apply formatting.

Use onError(error, operation) to handle formatter failures or rejected save and format hooks. operation is "save" or "format". A formatter failure leaves the source unchanged and does not call onFormat.