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 🙏

© 2024 – Pkg Stats / Ryan Hefner

json-forth

v1.0.0

Published

An interpreter for concatenative languages with JSON syntax.

Downloads

3

Readme

json-forth

An interpreter for concatenative languages with JSON syntax.

This interpreter implements a simple, generic class of homoiconic concatenative language designed for ease of interpretation and ease of synthesis; it is not intended primarily to be written or read by humans, although it certainly can be. The specific language to interpret is determined by an input op table.

The module exports a single interpret function with the signature interpret(opTable: OpTable, ast: any[], stack: any[], ctx?: Object): Promise<any[]>.

  • opTable is an object whose keys map to Operator functions, with the signature (interp: (code: any, ...args: any[]) => Promise<any[]>, ctx: Object, ...args: any[]) => Promise<any[]>. The first argument to an operator function is recursive callback into the interpreter, which allows for executing nested code blocks; this facility would be used by the implementation of, e.g., conditionals or loops.
  • ast is an array of containing the code/data to be executed.
  • stack is an array to use as the starting state of the program data stack.
  • ctx is an arbitrary object which will be passed in to all operations which can be used to hold arbitrary mutable context data. If no explicit context is provided, an empty object is created for internal use.

The contents of the ast array are interpreted as follows:

  • Strings beginning with "#" are treated as calls to built-in functions to be looked up in the op table.
  • Embedded arrays are contextually treated either as anonymous function definitions or data lists, either of which will be pushed onto the data stack. (If a subsequent function call passes the array to interp for evaluation, then it is code; otherwise, it is data.)
  • All other JSON values are treated as functions that simply place their own value onto the data stack. E.g., 1 just pushes the numeric value 1 onto the data stack, "hello" pushes the string "hello" onto the data stack, etc.