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

spoiler-friendly-hints

v1.0.5

Published

Converts plaintext into a simple html format with nested collapsible sections

Readme

spoiler-friendly-hints

Converts plaintext into a simple html format with nested collapsible sections.

Includes a handful of presentational options and hash-based navigation history.

Use

import { convert } from 'spoiler-friendly-hints';

const plaintextInput = `...`;
const htmlOutput = convert(plaintextInput, {
  // default values for options
  preamble: true,
  title: '',
  preambleUrl: '',
  colorText: '#FFF',
  colorBg: '#000',
  colorAccent: '#FFC',
  indent: /(^\t*)(.*$)/,
  highlight: /!!!/,
});

Input format

Each line may include nested children, indicated by their indent level (by default tabs are used, but this can be configured to use something else, e.g. indent: /(^(?:\s{2})*)(.*$)/ will use 2 spaces). Lines which have no nested children will be presented as plaintext. Extra blank lines are ignored and can be used to space out entries.

How you format the text is entirely up to you. You might use a question and answer format, simple statements, or even raw HTML.

Sample input

	Did you check under the sofa?
		It's not there.
	Did you check by the entrance?
		It's not there.
	Did you check inside the bathroom?
		Did you shut the door after you?
			!!! Did you check every surface?
				It's in the bathroom, behind the door, on the back wall.

Sample output

More examples are available in the test files (e.g. ./src/index.test - default values.snapshot.html).