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

@markplus/core

v1.0.6

Published

markplus

Readme

MarkPlus

A lightweight, programmable superset of Markdown — with variables, conditionals, loops, imports, progress bars, and more.

Overview

MarkPlus enhances standard Markdown with programming-style features while keeping syntax clean and readable. It compiles seamlessly to plain Markdown or HTML, making it ideal for templates, dynamic docs, notes, and structured content.

Features

  • Variables – Define and reuse values with @set and {{var}}
  • Conditionals@if / @elseif / @else / @end
  • Loops – Simple iteration with @for
  • File Imports – Modularize with @include (relative paths supported)
  • Inline Comments@// comment (works anywhere in a line)
  • Progress Bars – Render with [process 75%]
  • Colored Text – Inline color syntax <span style="color:blue">text</span>
  • Todo Lists – Extended checkbox support
  • Block Containers – Styled blocks like :::tip / :::warn

Quick Start

1. Write a .mplus file

@// This is a comment
@set version=0.1.0
@set title=MarkPlus

@if version==0.1.0
# {{title}} (v{{version}})
@else
# {{title}} (Unknown version)
@end

Progress:
[process 70%]

[blue]Version: {{version}}[/]

@include ./module.mplus

2. Compile

const fs = require('fs');
const path = require('path');
const MarkPlusCompiler = require('./src/MarkPlusCompiler');

const compiler = new MarkPlusCompiler();
const inputPath = path.resolve(__dirname, 'test.mplus');
const source = fs.readFileSync(inputPath, 'utf8');

const output = compiler.compile(source, inputPath);
fs.writeFileSync('output.md', output);

3. Run

npm run mplus yourfile.mplus

Systax Reference

Variables

@set name=MarkPlus
@set version=0.1.0

Hello, {{name}} v{{version}}

Conditions

@set score=88

@if score==100
Perfect!
@elseif score>90
Excellent
@elseif score>60
Pass
@else
Fail
@end

Loops

@for lang:JavaScript,TypeScript,Python
- Learn {{lang}}
@endmplus

Imports

@include ./header.mplus
@include ./sections/part1.mplus;

Comments

@// Full line comment
Hello @// inline comment

Progress Bars

Colored Text

Error Info Custom color

API

MarkPlusCompiler

compile(input: string, filePath?: string): string;
  • input: raw .mplus content
  • filePath: absolute path for resolving relative @include

Cli

const inputFile = process.argv[2];

VSCode Syntax Highlighting

Now developing.

Common Issues

@include ENOENT error

  • Cause: relative path not resolved correctly
  • Fix: pass the absolute path of the source file to compile()

@// not stripping correctly

  • Fix: use split('@//')[0] to trim inline comments

Conditionals rendered as plain text

  • Fix: use startsWith('@elseif') without trailing space

License

MIT (c)2026, Sunleo1230, All rights reserved.