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

@mdscript/mds-napi

v0.4.3

Published

MDS compiler native Node.js bindings (napi-rs)

Readme

@mdscript/mds-napi

Native Node.js bindings for the MDS (Markdown Script) compiler, built with napi-rs.

This is the high-performance backend used by @mdscript/mds on Node.js. Most users should depend on @mdscript/mds, not this package directly@mdscript/mds loads this native addon automatically and falls back to @mdscript/mds-wasm when a prebuilt binary is unavailable.

How it loads

This host package contains only the loader (index.js) and TypeScript types (index.d.ts). The compiled .node binaries ship in per-platform packages declared as optionalDependencies, filtered by os/cpu/libc:

| Platform package | Target | |------------------|--------| | @mdscript/mds-napi-darwin-arm64 | macOS Apple Silicon | | @mdscript/mds-napi-darwin-x64 | macOS Intel | | @mdscript/mds-napi-linux-x64-gnu | Linux x64 (glibc) | | @mdscript/mds-napi-linux-x64-musl | Linux x64 (musl) | | @mdscript/mds-napi-linux-arm64-gnu | Linux arm64 (glibc) | | @mdscript/mds-napi-linux-arm64-musl | Linux arm64 (musl) | | @mdscript/mds-napi-win32-x64-msvc | Windows x64 |

index.js selects the matching binary at runtime from process.platform, process.arch, and (on Linux) the detected libc.

API

const { compile, compileFile, check, checkFile, lint, lintFile, lintVirtual } = require('@mdscript/mds-napi');

compile(source, opts?)

Compile an MDS source string. Returns a discriminated-union result object:

  • Markdown: { kind: "markdown", output: string, warnings: string[], dependencies: string[], sourceMap?: object }
  • Messages: { kind: "messages", messages: [{role,content},...], warnings: string[], dependencies: string[] }

Options:

  • basePath (string) — base directory for @import resolution; defaults to cwd.
  • vars (object) — runtime variable overrides.
  • sourceMap (boolean) — generate a Source Map v3 document; result gains sourceMap. For string-source compiles sources[0] is "input.mds".
  • sourcesContent (boolean) — embed original source text in the map (requires sourceMap). ⚠ Privacy: embeds the full template source.

compileFile(path, opts?)

Same result shape as compile. Options: vars, sourceMap, sourcesContent. basePath is not accepted — the base directory is derived from the file path.

check(source, opts?) / checkFile(path, opts?)

Validate without rendering. Returns { warnings: string[] }. Options: basePath, vars (check only; checkFile: vars only). Source-map options are not accepted — check does not generate output.

lint(source, opts?) / lintFile(path, opts?) / lintVirtual(modules, entry, opts?)

Static analysis. Returns the canonical lint JSON: { version: 1, files: [{file, diagnostics: [{rule, severity, message, help: string | null, fixable, fix_edits: ... | null, span: LintSpan | null},...]},...], truncated: bool, lint_warnings?: string[] }

help, span, and fix_edits are always-present keys in the JSON object; their value is null when the rule emits no hint, produces no source span, or carries no fix edits respectively.

Options: basePath (lint only — lintFile derives the base from the file path; lintVirtual resolves against the module map), vars, rules (Record<string, "off"|"info"|"warn"|"error">). Unknown rule names in rules emit a warning and lint continues — the unknown name has no effect but result.lint_warnings (a string[] field, absent when empty) is populated so callers can surface the issue; unknown severity values throw mds::invalid_options.

files[].file key: lint() sets this to "input.mds" (string-source); lintFile() sets it to the file's path; lintVirtual() sets it to the caller-supplied entry key. The CLI additionally relabels stdin input as "<stdin>" — this asymmetry does not apply to the napi binding.

See index.d.ts for the full typed surface.

License

MIT — see LICENSE.