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

plain-text-box

v0.1.1

Published

Auto-expanding plain text editor with committed and tentative text

Readme

Auto-expanding plain text editor with tentative text

When offering an editable text area to users that is augmented with a service such as an AI assistant, code completion or speech recognition, we need to distinguish between committed text (typed or accepted by the user) and tentative text (code completion prompt or provisional text emitted by speech recognition). While many applications with rich text editors have this capability, this web component offers a simple solution with minimal dependencies.

Refer to the demo page for an interactive example.

Installation

npm install plain-text-box

Usage

Register web component

import { registerPlainTextBox } from "plain-text-box";

document.addEventListener("DOMContentLoaded", () => {
    registerPlainTextBox();
});

Connect web component

<plain-text-box disabled max-rows="5" min-rows="2"
    placeholder="Type text here...">
</plain-text-box>

Use CSS variables to customize appearance

plain-text-box {
    border: thin solid black;
    border-radius: 10px;
    padding: 5px;
    max-width: 100%;
    width: 640px;
    --text-color-active: blue;
    --text-color-inactive: lightgray;
    --text-color-tentative: gray;
}

Internals

Structurally, the web component encapsulates an HTML <textarea> element that intercepts user input and a <div> element that is responsible for visualization. The characters typed into <textarea> are invisible but immediately appear in the <div> element. While a <textarea> can only have a single font color and size, a <div> allows us to fine-tune formatting, and apply a darker color to committed text and a lighter color to tentative text.