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 🙏

© 2024 – Pkg Stats / Ryan Hefner

remark-comment

v1.0.0

Published

Remark plugin to support comments

Downloads

3,520

Readme

remark-comment

Parse HTML style comments as a different node type so it can be ignored during serialization.

Install and usage

npm install remark-comment
import { unified } from 'unified'
import remarkParse from 'remark-parse'
import remarkComment from 'remark-comment'

unified().use(remarkParse).use(remarkComment)

For more help with unified, please see the docs for unified and remark.

This package also exports its micromark and [mdast-util] plugins:

import {
  comment,
  commentHtml,
  commentFromMarkdown,
  commentToMarkdown,
} from 'remark-comment'

Options:

The remarkComment and commentFromMarkdown functions take the options:

  • ast: If true, a { type: "comment" } node will be included in the resulting AST. This is useful if you want to do post-processing and stringify back to markdown. Default: false.

Example

# This file

<!-- contains a comment -->

And a paragraph

Renders to:

<h1>This file</h1>
<p>And a paragraph</p>

Motivation

This package was created after realizing that MDX lacked support for HTML style comments. When trying to migrate an existing collection of markdown files to MDX, hitting syntax errors for HTML comments was a non-starter. Rather than go modify all those files to use a (more awkward) JSX expression comment, I created this plugin to add back this support.

However, I found this useful when used outside of MDX. Common markdown interprets an HTML comment as an HTML block, and during serialization will pass it directly through to the final HTML document. I typically do not want my markdown comments appearing in my final HTML documents, and this plugin achieves this effect.

Caveats

This plugin must be added after MDX, otherwise you will see this error:

Unexpected character `!` (U+0021) before name, expected a character that can start a name, such as a letter, `$`, or `_` (note: to create a comment in MDX, use `{/* text */}`)

In a unified pipeline:

unified().use(remarkMDX).use(remarkComment)

Comments cannot be used within a JSX body. JSX is still JSX. Comments must appear outside of JSX.

Similarly, when used with common markdown, a comment cannot be used within an HTML body. If it does it will be parsed as an HTML comment as part of the HTML body and emitted to the final document.