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

@lacelang/executor

v0.1.1

Published

Reference TypeScript executor for the Lace probe scripting language

Downloads

171

Readme

lacelang-executor (TypeScript)

Reference TypeScript executor for Lace -- the reference implementation with 100% spec conformance. Runs .lace scripts against real HTTP endpoints and emits ProbeResult JSON.

Parsing and semantic validation are delegated to @lacelang/validator -- this package contains only the runtime (HTTP client, assertion evaluation, cookie jars, extension dispatch). See lace-spec.md section 15 for the validator / executor package separation rule.

Install

npm install @lacelang/executor

This automatically installs @lacelang/validator as a dependency.

Or from source:

npm install git+https://github.com/tracedown/lacelang-js-executor.git

CLI

# Parse (delegates to validator)
lacelang-executor parse script.lace

# Validate (delegates to validator)
lacelang-executor validate script.lace --vars-list vars.json

# Run -- full HTTP execution
lacelang-executor run script.lace \
    --vars vars.json \
    --prev prev.json

# Enable extensions
lacelang-executor run script.lace --enable-extension laceNotifications

All subcommands support --pretty for indented JSON.

Library

import { LaceExecutor } from "@lacelang/executor";

// Point to the lace/ directory -- config loaded once
const executor = new LaceExecutor("lace");

// Prepare a probe by name -- resolves to lace/scripts/health/health.lace
// AST is parsed and validated once, reused across runs
const probe = executor.probe("health");

// Run -- returns a ProbeResult dict
const result = await probe.run({ base_url: "https://api.example.com" });

// Run again -- prev result from last run injected automatically
const result2 = await probe.run();

// One-shot execution (no probe caching, no prev tracking)
const result3 = await executor.run('get("https://example.com").expect(status: 200)');

Project layout

my-project/
  lace/
    lace.config                      # executor config (auto-discovered)
    extensions/                      # third-party extensions
    scripts/
      health/
        health.lace                  # script (name = directory name)
        vars.json                    # default variables

Configuration

# lace/lace.config

[executor]
maxRedirects = 10
maxTimeoutMs = 300000

# Staging overlay -- deep-merged on top of base
[lace.config.staging]
[lace.config.staging.executor]
maxTimeoutMs = 60000
const executor = new LaceExecutor("lace", { env: "staging" });

Extensions

Built-in extensions (laceNotifications, laceBaseline) are bundled and activated via config or constructor:

// Via constructor
const executor = new LaceExecutor("lace", {
  extensions: ["laceNotifications"],
});

// Via lace.config
// [executor]
// extensions = ["laceNotifications"]

Register third-party extensions:

// Directory (finds myext.laceext + myext.config inside)
executor.extension("lace/extensions/myext");

// Explicit paths
executor.extension("path/to/custom.laceext", "path/to/custom.config");

Low-level API

The stateless runScript() function is available for callers that need full control over parsing, validation, and config:

import { parse } from "@lacelang/validator";
import { runScript, loadConfig } from "@lacelang/executor";
import * as fs from "node:fs";

const ast = parse(fs.readFileSync("script.lace", "utf-8"));
const config = loadConfig({ explicitPath: "lace.config" });

const result = await runScript(ast, { key: "val" }, null, null, null, null, null, config);

Responsible use

This software is designed for monitoring endpoints you own or have explicit authorization to probe. See NOTICE for the full statement.

License

Apache License 2.0