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

@cinderblock-lang/compiler

v0.0.2

Published

The compiler for the CinderBlock programming language

Readme

CinderBlock

Welcome to the CinderBlock programming language! This is very much in infancy but it should run well, if slowly, so you can have a go at getting your projects off of the ground with it.

The language is an entirely pure functional one but JavaScript functions may be injected and they could theoretically have side effects. While it is possible to inject side effects this way, please do not attempt it. Execution order is not guaranteed and a variable may not be calculated if it is not referenced. As such, it would be impossible to assume that a side effect will always work.

Repo Directory

  • compiler is the actual compiler and runtime (runtime will be separated soon)
  • tests are a series of Node Tests which assert the language functionality. They still need a lot of expanding.
  • server is a super lightweight server framework to show off the options with the language.
  • budget-tracker is a very early days example app to show how the language may be used in the real world.

Making the Language Useful

Please see the server directory for an example of a basic server framework which utilises a simple JavaScript wrapper around CinderBlock. This framework uses ExpressJS and then utilises the ability to tag let instances (which is native to CinderBlock). In order to perform data mutations, a handler may return a list of mutative operations to call with a server response. The server then invokes the implementations of those operations, which are written in TypeScript, before sending the response.

For an example of this in use, see the budget-tracker app, which is an incredibly bare bones project that I set up, in order to test out the language in a more "real world" example as I coded it.

Where Things Are

  • A TypeScript written compiler which compiles to a JavaScript object of instructions, which are pre linked.
  • A TypeScript written runner which reads the object and executes the instructions.
  • The ability to inject in JavaScript functions.
  • Some standard library features which are simply thin wrappers around NodeJS abilities.

The Next Steps

  • Write a simple CLI to invoke let instances directly.
  • Update the JavaScript object that comes out of the compiler to use a byte encoding into a buffer.
  • Update the TypeScript runner to be written in C++ and compile to Web Assembly.
  • Allow the injection of either JavaScript or C++ functions.
  • Fill out the standard libraries to have more use cases.

The Final Steps

  • Rewrite the compiler in CinderBlock.

Setting Up Your Own Basic Project

First install cinderblock

npm install @cinderblock-lang/compiler

Create an entrypoint.

import { Project } from "@cinderblock-lang/compiler";
import path from "node:path";

async function main() {
  const instance = new Project(path.resolve(import.meta.dirname));

  const binary = instance.binary({
    hello(_s: string) {
      return "I am a " + _s;
    }
  });

  console.log(await binary.run("startup",{ func_arg: "I am an argument" }));
}

Finally, create a CinderBlock file.

extern hello (): string;

let startup (func_arg: string) = "Hello " + func_arg + " and also hello " + ("global" -> hello);

Make sure your you have these fields in your package.json

{
  "type": "module",
  "main": "typescript-file-from-above.ts"
}

and run

node .

This will then print the following to the console.

Hello I am an argument and also hello I am a global

Installing the VsCode Extension

The VsCode extension is currently not on the market place. Simply run the bundle NPM script in the vscode-extension folder and then install from the generated vsix file. This should give you basic functionality such as;

  • Syntax highlighting
  • Go to definition
  • Diagnostic issues