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

@mctools/format

v1.1.3

Published

Format .zs files by using ESLint for typescript

Readme

Format .zs files by using ESLint for typescript

The pipeline is:

.zs ──Peggy──▶ .ts (with markers) ──ESLint --fix──▶ .ts ──regex revert──▶ .zs

The Peggy grammar (src/zenscript.peggy) lexes ZenScript and emits valid TypeScript sprinkled with block-comment markers. ESLint formats it like any other TS file, then a disciplined set of regexes (see src/tsToZs.ts) maps the markers back to ZS.

Requirements:

  • eslint@^9 is a peer dependency — install it in the host project alongside whatever ESLint config you want applied to the intermediate .ts files (e.g. @antfu/eslint-config). The package intentionally provides no config of its own; the whole point is to reuse yours.

Programmatic API:

import { revert, zsToTs } from '@mctools/format'

const result = zsToTs(zsSource)            // pure: string → { ok, ts } | { ok: false, error }
if (result.ok) {
  // result.ts contains marker-laden TypeScript
  const back = revert(/* TS source after ESLint */)
}

zsToTs / revert are pure (string in → string out). For batch file I/O see convertToTs from @mctools/format/dist/formatFile.

Usage

  1. Install latest NodeJS for Windows or Unix

  2. Open console, navigate to your Minecraft directory (one with the mods/ directory or options.txt file)

    > cd C:/Instances/MyModpack
  3. Run:

    > npx @mctools/format --help

Options

Format .zs files by using ESLint for typescript (@mctools/format v0.0.0)

USAGE @mctools/format [OPTIONS] <FILES>

ARGUMENTS

  FILES    Path to file / files for formatting    

OPTIONS

   -i, --ignore    Same as --ignore-pattern for ESLint
    -p, --pause    Pause and ask before linting       
  -v, --verbose    Show timing for each step

Author

  • https://github.com/Krutoy242

Other tools