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

@adobe/helix-md2jcr

v1.2.9

Published

Helix Service that converts markdown to JCR content structure

Downloads

1,409

Readme

Helix Markdown to JCR

A library that converts markdown to JCR.

Status

codecov GitHub license GitHub issues semantic-release

Development

Install all dependencies by running:

npm install

Usage

Installation

You can install the package via npm:

npm install @adobe/helix-md2jcr

Or use it directly with npx without installing:

npx @adobe/helix-md2jcr path/to/content.md

Converting Markdown to JCR Nodes

The package includes a CLI tool md2jcr that converts markdown files to JCR XML format.

Basic usage:

npx @adobe/helix-md2jcr path/to/content.md

Convert a single file:

md2jcr test/fixtures/simple.md

Convert all markdown files in a directory:

md2jcr test/fixtures/

View output in console with verbose flag -v:

md2jcr test/fixtures/simple.md -v

View decoded XML output with -v and -d flags:

md2jcr test/fixtures/simple.md -v -d

Use custom Universal Editor files from a directory:

md2jcr content.md -ue path/to/ue-files-directory

The converter will generate a .xml file alongside the markdown file containing the JCR structure. This can be used to check for potential content changes due to conversion.

Command-Line Options

  • -v, --verbose - Print the XML output to the console
  • -d, --decode - Decode HTML entities in the XML output (use with -v)
  • -ue, --ue-files <directory> - Specify a directory containing Universal Editor configuration files

Example directory structure:

ue-files/
  ├── component-models.json
  ├── component-definition.json
  └── component-filters.json

Programmatic Usage

You can also use the library programmatically in your Node.js code:

import { md2jcr } from '@adobe/helix-md2jcr';

const markdown = '# Hello World\n\nThis is a test.';
const options = {
  models: [...],
  definition: {...},
  filters: [...]
};

const xml = await md2jcr(markdown, options);
console.log(xml);

Baseline XML Files

Running the ./baseline-tests.sh script will detect any md file under test/fixtures and execute the convert2jcr node script.
The script will generate new xml files beside the md files it locates. This is helpful when making changes to the converter and you want to see if the changes have any impact on the output. By using git diff, you will see the new changes in the xml files. If you are satisfied with the changes, you can commit the new xml files.

Running Tests

Simply execute the following command to run the tests:

npm test