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 🙏

© 2025 – Pkg Stats / Ryan Hefner

remark-ins

v1.2.2

Published

Remark plugin to add ins element in markdown

Downloads

22,743

Readme

Become a sponsor 🚀

If you find remark-ins useful in your projects, consider supporting my work.
Your sponsorship means a lot 💖

Be the first sponsor and get featured here and on my sponsor wall.
Thank you for supporting open source! 🙌

remark-ins

npm version npm downloads publish to npm code-coverage type-coverage typescript license

This package is a unified (remark) plugin to add custom <ins> element in markdown.

unified is a project that transforms content with abstract syntax trees (ASTs) using the new parser micromark. remark adds support for markdown to unified. mdast is the Markdown Abstract Syntax Tree (AST) which is a specification for representing markdown in a syntax tree.

This plugin is a remark plugin that transforms the mdast.

When should I use this?

remark-ins is useful if you want to add a <ins> element in markdown, which represents a range of text that has been added to a document.

You can easily create <ins> element with remark-ins.

Installation

This package is suitable for ESM only. In Node.js (version 16+), install with npm:

npm install remark-ins

or

yarn add remark-ins

Usage

use ++ around the content

Say we have the following file, example.md, which consists some flexible markers.

++inserted text++

And our module, example.js, looks as follows:

import { read } from "to-vfile";
import remark from "remark";
import gfm from "remark-gfm";
import remarkRehype from "remark-rehype";
import rehypeStringify from "rehype-stringify";
import remarkIns from "remark-ins";

main();

async function main() {
  const file = await remark()
    .use(gfm)
    .use(remarkIns)
    .use(remarkRehype)
    .use(rehypeStringify)
    .process(await read("example.md"));

  console.log(String(file));
}

Now, running node example.js yields:

<p><ins class="remark-ins">inserted text</ins></p>

Without remark-ins, you’d get:

<p>++inserted text++</p>

[!CAUTION] The double plus signs must be adjacent to the content.
The content must be wrapped with double plus signs, not singular at any side.\

Here are some bad usage, and will not work.

++text with bad wrapped+

+text with bad wrapped++

++ text with unwanted space++

++text with unwanted space ++

It is more flexible and powerful

As of version ^1.1.0, remark-ins can handle also the syntax containing other markdown phrases like strong, emphasis, link etc. For example:

++**inserted bold content**++

++_inserted italic content_++

++[inserted link](https://google.com)++
<p>
  <ins class="remark-ins">
    <strong>inserted bold content</strong>
  </ins>
</p>
<p>
  <ins class="remark-ins">
    <em>inserted italic content</em>
  </ins>
</p>
<p>
  <ins class="remark-ins">
    <a href="https://google.com">inserted link</a>
  </ins>
</p>

Options

There is no option for remark-ins.

Example:

~~deleted content~~ and ++inserted content++

**++inserted bold content++** and ++**inserted bold content**++

### Heading with ++inserted content++

is going to produce as default:

<p>
  <del>deleted content</del>
   and 
  <ins class="remark-ins">inserted content</ins>
</p>
<p>
  <strong><ins class="remark-ins">inserted bold content</ins></strong>
   and 
  <ins class="remark-ins"><strong>inserted bold content</strong></ins>
</p>
<h3>Heading with <ins class="remark-ins">inserted content</ins></h3>

You can use the ins syntax in the tables, headings, lists, blockquotes etc. For detailed examples, you can have a look at the test files in the github repo.

Syntax tree

This plugin only modifies the mdast (markdown abstract syntax tree) as explained.

Types

This package is fully typed with TypeScript.

Compatibility

This plugin works with unified version 6+ and remark version 7+. It is compatible with mdx version 2+.

Security

Use of remark-ins does not involve rehype (hast) or user content so there are no openings for cross-site scripting (XSS) attacks.

My Plugins

I like to contribute the Unified / Remark / MDX ecosystem, so I recommend you to have a look my plugins.

My Remark Plugins

My Rehype Plugins

  • rehype-pre-language – Rehype plugin to add language information as a property to pre element
  • rehype-highlight-code-lines – Rehype plugin to add line numbers to code blocks and allow highlighting of desired code lines
  • rehype-code-meta – Rehype plugin to copy code.data.meta to code.properties.metastring
  • rehype-image-toolkit – Rehype plugin to enhance Markdown image syntax ![]() and Markdown/MDX media elements (<img>, <audio>, <video>) by auto-linking bracketed or parenthesized image URLs, wrapping them in <figure> with optional captions, unwrapping images/videos/audio from paragraph, parsing directives in title for styling and adding attributes, and dynamically converting images into <video> or <audio> elements based on file extension.

My Recma Plugins

  • recma-mdx-escape-missing-components – Recma plugin to set the default value () => null for the Components in MDX in case of missing or not provided so as not to throw an error
  • recma-mdx-change-props – Recma plugin to change the props parameter into the _props in the function _createMdxContent(props) {/* */} in the compiled source in order to be able to use {props.foo} like expressions. It is useful for the next-mdx-remote or next-mdx-remote-client users in nextjs applications.
  • recma-mdx-change-imports – Recma plugin to convert import declarations for assets and media with relative links into variable declarations with string URLs, enabling direct asset URL resolution in compiled MDX.
  • recma-mdx-import-media – Recma plugin to turn media relative paths into import declarations for both markdown and html syntax in MDX.
  • recma-mdx-import-react – Recma plugin to ensure getting React instance from the arguments and to make the runtime props {React, jsx, jsxs, jsxDev, Fragment} is available in the dynamically imported components in the compiled source of MDX.
  • recma-mdx-html-override – Recma plugin to allow selected raw HTML elements to be overridden via MDX components.
  • recma-mdx-interpolate – Recma plugin to enable interpolation of identifiers wrapped in curly braces within the alt, src, href, and title attributes of markdown link and image syntax in MDX.

License

MIT License © ipikuka