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

@code-fixer-23/mace-node

v2.0.0

Published

Official Node.js bindings for Mace

Downloads

246

Readme

@code-fixer-23/mace-node

Official ESM-only Node.js bindings for Mace.

Status

This package provides a Node.js API around the mace CLI. Supported release binaries are included in the package and selected automatically for the current platform. Pass macePath when a project needs a different Mace executable.

Development

This package was scaffolded with Vite via jpd create vite. Scoped npm packages are published with publishConfig.access = "public".

cd packages/node
jpd install
jpd run build

Usage

import { json, output, transform } from '@code-fixer-23/mace-node'

const value = await json('./config.mace')
const inlineValue = await transform('{ name: "Mace", }')
const runtimeValue = await json('./runtime.mace', {
  input: '{ env: "prod", }',
})
const outputRecord = await output('./config.mace')

API

  • json(path, { input?, macePath?, cwd? }?)Promise<MaceRecord>
  • transform(source, { input?, macePath?, cwd? }?)Promise<MaceRecord>
  • jsonText(path, { input?, macePath?, cwd? }?)Promise<MaceRecord>
  • output(path, options?)Promise<MaceRecord>
  • importJson(input, options?)Promise<MaceRecord>
  • importYaml(input, options?)Promise<MaceRecord>
  • importToml(input, options?)Promise<MaceRecord>
  • importFile(path, options?)Promise<MaceRecord>

macePath is optional; the package uses its bundled platform binary when it is not provided.

Records and errors

transform writes Mace source to a temporary file, evaluates it through the CLI, and deserializes its JSON result into a MaceRecord. jsonText is retained as an alias for json; output evaluates the supplied Mace file; and import* evaluates the Mace source generated by the CLI import command. A MaceRecord contains strings, numbers, booleans, nested records, and arrays.

CLI failures reject with MaceError. Alongside message and exitCode, its diagnostic provides a best-effort structured view of the CLI stderr: category, code, message, range.start.line, range.start.column, and path. The current CLI text protocol does not always provide every field, so category, code, range, and path are optional.