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

the-super-tiny-interpreter

v1.0.3

Published

Explain what a closure is by writing a JavaScript interpreter in JavaScript

Downloads

6

Readme

The Super Tiny Interpreter

build status test coverage

Let's explain what a closure is by writing a JavaScript interpreter in JavaScript.

This project is still a work in progress, but feel free to poke around and check out the unit tests.

Disclaimer

The goal of this project is not to make a spec-compliant or blazing-fast interpreter. The goal, however, is to interpret a tiny subset of JavaScript features in super-easy-to-read™ code.

Supported Syntax

  1. Numbers, Booleans, null, and undefined
12 // Numeric Literal
true // Boolean Literal
null // Null Literal
undefined // Do you know that `undefined` is actually an identifier? Paul Irish calls shadowing it the "Asshole Effect".
  1. Variable, a.k.a. Identifier
foo
  1. Binary Operators
+, -, *, /, ==, ===, !=, !==, <, <=, >, >=
  1. Unary Operators
!, -
  1. Conditional Expression, a.k.a. the ternary operator
test ? consequent : alternate
  1. Arrow Function Expression
  • Notice that we didn't implement the traditional function syntax. Arrow functions FTW!
(x) => x + 1

(x) => {
  const y = x + 100;
  return y * y;
}
  1. Call Expression
foo(1, 2, 3)
  1. Variable Declaration Statement
  • Notice that we only support const for now and there's NO mutation (assignment) in our language.
    • That means we can initialize stuff once and only once
    • And of course const foo is not valid JavaScript
  • If you are familiar with Scheme/OCaml, then const LHS = RHS behaves just like a letrec.
const foo = 12;

const fact = (x) => x < 2 ? 1 : x * fact(x - 1);