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

langsagne

v0.1.0

Published

minimal programming language parser and execution experiment

Readme

langsagne

Minimal programming language parser and execution experiment

Play

bun run test
bun run exec examples/assignment
bun run exec -- --trace examples/loop
bun run exec -- --step examples/if-else

Programs live in examples/. Use Enter or n for next, p for previous, and q to quit in step mode.

Language

Syntax

  • numbers: 1, 42
  • strings: "hello", 'path/to/file'
  • variables: a, count_1
  • assignment: a = 1 + 2
  • arithmetic: +, -, *, / (numeric only)
  • comparison: < (returns 1 or 0)
  • parentheses: (1 + 2) * 3
  • blocks: { ... }
  • if (expr) { ... } else { ... }
  • while (expr) { ... }
  • fn name(a, b) { ... }
  • return expr;
  • function calls: add(1, 2)
  • statements end with ;
  • last expression value is the program result

Not supported yet: string +, ==, arrays, comments, forward references.

System calls

| Call | Args | Result | | --- | --- | --- | | print(...) | zero or more expressions | prints to stdout, leaves last arg in ax | | assert(expr) | one expression | throws if falsy | | clock() | none | Date.now() |

Functions must be declared before use. Calls check arity (add(1) is an error).

Examples

a = 1;
b = 2 + a;
b;
→ 3
i = 0;
sum = 0;
while (i < 2) {
  sum = sum + i;
  i = i + 1;
}
sum;
→ 1
value = 0;
if (value) {
  result = 1;
} else {
  result = 2;
}
print('result =', result);
result;
→ prints: result = 2
→ returns: 2
fn add(a, b) {
  return a + b;
}
add(1, 2);
→ 3
assert(1);
assert(1 + 2 < 4);
assert(2 + 2 < 4);
→ RUNTIME ERR: assert failed
   at line 3

API

import { execute } from './src/index.ts'

execute('a = 1; b = a + 2; b;') // 3

execute(code) compiles and runs source, then returns the final value in ax.

For directive-level debugging:

import { inspect } from './src/index.ts'

const { directives, trace, result } = inspect('a = 1; a;')

Runtime code is under src/ (lexer/, compiler/, runtime/, debug/). Tests are in test/.

Plan

See docs/design.md for the current gaps between this project and the c4-inspired language target.