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

tinymce-schema

v1.0.2

Published

Ability to add schema to elements inside TinyMCE

Downloads

16

Readme

Schema TinyMCE Plugin

This plugin helps the content editor add Schema values to content inside the WYISIWYG editor.

Installation

  1. Via NPM:
$ npm i tinymce-schema
  1. Via Github:
$ git clone https://github.com/nomensa/tinymce-schema

User workflow

  1. Highlight text;
  2. Press the "Add schema" button;
  3. A popup window appears with the title of "Adding schema" and field label "Schema property"
  4. Add the schema value as the "Schema property'
  5. Press "Ok"

Developer workflow

  1. The developer adds a schema type to the template, i.e:
itemtype="http://schema.org/Event"
  1. The WYSIWYG content editor highlights text and adds a property 'value' to the text;
  2. The plugin (always) adds a 'itemprop' attribute to the text with a <span> tag, i.e.:
<span itemprop="..."> Highlighted text </span>
  1. The plugin uses the value provided by the content editor inside the value of the 'itemprop' attribute, i.e.:
<span itemprop="event-title"> Highlighted text </span> 

The development server

By running the npm start command you start the development server and open a browser window with an instance of TinyMCE with your plugin added to it. This window will reload automatically whenever a change is detected in the index.html file in the static folder or in one of the JavaScript files in the src directory.

The production build

By running the npm run build command Webpack will create a dist directory with a child directory with the name of your plugin (schema) containing three files:

  • plugin.js - the bundled plugin
  • plugin.min.js - the bundles, uglified and minified plugin
  • LICENSE - a file explaining the license of your plugin (copied over from src/LICENSE)