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

@manifesto-ai/compiler

v3.9.0

Published

Manifesto Compiler - MEL (Manifesto Expression Language) to DomainSchema compiler

Readme

@manifesto-ai/compiler

Compiler translates MEL (Manifesto Expression Language) into DomainSchema for Manifesto Core.


What is the Compiler?

The compiler is the MEL frontend for Manifesto. It tokenizes, parses, validates, and lowers MEL source into a DomainSchema that Core can evaluate deterministically.

MEL source -> Compiler -> DomainSchema -> Core

What the Compiler Does

| Responsibility | Description | | --- | --- | | Parse MEL | Tokenize and parse MEL into an AST | | Validate | Scope, typing, and semantic checks aligned to the current compiler contract | | Generate IR | Produce DomainSchema for Core | | Lower system values | Optional lowering of $system.* into explicit effects |


What the Compiler Does NOT Do

| NOT Responsible For | Who Is | | --- | --- | | Execute effects | Host | | Apply patches | Core | | Govern authority or seal history | @manifesto-ai/governance + @manifesto-ai/lineage | | Bind UI or caller integrations | SDK / application layer |

Current MEL/compiler highlights:

  • available when remains the coarse action gate.
  • dispatchable when is the fine bound-intent legality gate.
  • Expression-level collection builtins include filter, map, find, every, and some.
  • Bounded parser-free sugar includes absDiff, clamp, idiv, streak, match, argmax, and argmin.
  • Current schema-position lowering supports Record<string, T> and T | null.

Installation

npm install -D @manifesto-ai/compiler
# or
pnpm add -D @manifesto-ai/compiler

Bundler Integration (unplugin)

The compiler uses unplugin to provide a unified MEL plugin for all major bundlers. One implementation, every bundler.

Vite

// vite.config.ts
import { defineConfig } from "vite";
import { melPlugin } from "@manifesto-ai/compiler/vite";

export default defineConfig({
  plugins: [melPlugin()],
});

Next.js / Webpack

// next.config.js
const mel = require("@manifesto-ai/compiler/webpack");

module.exports = {
  webpack: (config) => {
    config.plugins.push(mel());
    return config;
  },
};

Rollup

// rollup.config.js
import { melPlugin } from "@manifesto-ai/compiler/rollup";

export default { plugins: [melPlugin()] };

esbuild

import { melPlugin } from "@manifesto-ai/compiler/esbuild";

await esbuild.build({ plugins: [melPlugin()] });

Rspack

const mel = require("@manifesto-ai/compiler/rspack");

module.exports = { plugins: [mel()] };

Node / tsx (ESM Loader)

npx tsx --loader @manifesto-ai/compiler/node-loader main.ts

Plugin Options

import { createCompilerCodegen } from "@manifesto-ai/codegen";

melPlugin({
  include: /\.mel$/,           // File filter (default: /\.mel$/)
  codegen: {
    emit: createCompilerCodegen(),
    timing: "transform",       // default: run during dev/build transforms
  },
});

codegen is an explicit emitter hook. @manifesto-ai/compiler does not import @manifesto-ai/codegen for you; install it only if you want MEL artifacts written during dev or build and inject the emitter yourself.

createCompilerCodegen() can be called with no options. In that default mode it uses the canonical domain plugin and writes <source>.domain.ts next to the compiled .mel file during transform. If you prefer build-end emission, set timing: "build" or timing: "both". You can still customize the pipeline:

import { createCompilerCodegen, createDomainPlugin } from "@manifesto-ai/codegen";

melPlugin({
  codegen: {
    emit: createCompilerCodegen({
      outDir: "src/generated",
      plugins: [createDomainPlugin({ interfaceName: "CounterDomain" })],
    }),
    timing: "build",
  },
});

Subpath Exports

| Export | Bundler | | --- | --- | | @manifesto-ai/compiler/vite | Vite | | @manifesto-ai/compiler/webpack | Webpack / Next.js | | @manifesto-ai/compiler/rollup | Rollup | | @manifesto-ai/compiler/esbuild | esbuild | | @manifesto-ai/compiler/rspack | Rspack | | @manifesto-ai/compiler/node-loader | Node ESM loader hooks |


CLI Usage

pnpm exec mel check path/to/domain.mel
pnpm exec mel compile path/to/domain.mel --pretty
pnpm exec mel compile path/to/domain.mel --stdout
pnpm exec mel parse path/to/domain.mel
pnpm exec mel tokens path/to/domain.mel

Node API

import { compile, check } from "@manifesto-ai/compiler";

const source = `
domain Counter {
  state { count: number = 0 }
  action increment() {
    when true { patch count = add(count, 1) }
  }
}
`;

const result = compile(source, { lowerSystemValues: true });

if (!result.success) {
  console.error(result.errors);
} else {
  console.log(result.schema);
}

const errors = check(source);

Compile Options

type CompileOptions = {
  skipSemanticAnalysis?: boolean;
  lowerSystemValues?: boolean;
};

Documentation

| Document | Purpose | | --- | --- | | MEL Overview | What MEL is and how to use it | | MEL Syntax | Grammar and syntax | | MEL Examples | Example library | | MEL Error Guide | Error codes and fixes | | Compiler Spec | Current full compiler and MEL spec | | Compiler FDR | Design rationale | | Compiler Compliance Suite | CCTS structure, rule modes, and execution guide |


License

MIT