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

datocms-plugin-lorem-ipsum

v0.2.6

Published

Fill your textual fields with dummy content

Readme

Lorem Ipsum Generator

Makes it easy to fill text-style fields with dummy content while authoring records in DatoCMS.

The plugin adds a Generate dummy text action to the field's dropdown menu (the "three dots" menu next to a field) on supported fields. Clicking the action populates the field with appropriate placeholder content; the field must be configured for the action to appear.

Supported field types

  • Single-line string (string)
  • Multi-paragraph text (text)
  • Structured Text (structured_text)

How the generated content adapts to the field

  • string fields — generates a short title-cased sentence by default. When the field's predefined-format validator is set to email or url, the plugin generates a realistic email address or URL instead.
  • text fields with the Markdown editor — generates Markdown with headings, paragraphs, lists, and blockquotes when the corresponding toolbar buttons are enabled.
  • text fields with the WYSIWYG editor — generates the same article shape rendered as HTML, again respecting the toolbar configuration.
  • text fields with any other editor — falls back to plain Lorem Ipsum paragraphs.
  • structured_text fields — generates Structured Text DAST nodes, including only the node and mark types allowed by the field's editor configuration.

How to enable it on a field

There are two ways to expose Generate dummy text on a field:

  1. Manually, by adding the plugin as a presentation addon on the field from the schema editor. Once added, the dropdown action appears on that field for editors.

  2. Automatically, by defining one or more auto-apply rules in the plugin's configuration screen. A rule is a combination of:

    • One or more field types (single-line string, multi-line text, Structured Text), and
    • A regular expression matched against the field's API key.

    Any field whose type and API key match at least one rule will surface the dropdown action without needing the addon to be added explicitly.

Configuration

Open the plugin's configuration screen (Configuration → Plugins → Lorem ipsum generator) to add or remove auto-apply rules. Each rule needs both a non-empty regexp and at least one selected field type; invalid regexps are silently skipped at runtime so a typo never breaks the editing experience.

Manually-added fields keep working regardless of whether any rule is configured.