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

walt-compiler

v0.21.0

Published

Alternative syntax for WebAssembly text format

Downloads

80

Readme

Walt Compiler

This is the main walt compiler package.

Install

npm install --save walt-compiler

API

type Compile = (source: string, options?: Options) => Result

Compile and run Walt code in browser:

import { compile } from 'walt-compiler';

const buffer = compile(`
  let counter: i32 = 0;
  export function count(): i32 {
    counter += 1;
    return counter;
  }
`).buffer();

WebAssembly.instantiate(buffer).then(result => {
  console.log(`First invocation: ${result.instance.exports.count()}`);
  console.log(`Second invocation: ${result.instance.exports.count()}`);
});

Compile and save a .wasm file via Node.js:

const { compile } = require('walt-compiler');
const fs = require('fs');

const buffer = compile(`
  let counter: i32 = 0;
  export function count(): i32 {
    counter += 1;
    return counter;
  }
`).buffer();

fs.writeFileSync('bin.wasm', new Uint8Array(buffer));

Result

type Result = {
  buffer: () => ArrayBuffer,
  ast: NodeType,
  semanticAST: NodeType
}

buffer()

Unique (across function calls) ArrayBuffer instance.

ast

The Program root node containing the source program without any type information. This is the node passed to semantic parser.

semanticAST

The Program root node containing the source program including the final type information. This is the AST version used to generate the final binary.

Options

type Options = {
  version?: number,
  encodeNames?: boolean,
  filename?: string,
  extensions: Array<Plugin>
}

version

The target WebAssembly Standard (not to be confused with compiler version) version to which the source should be compiled to. Currently supported versions: 0x01

encodeNames

Whether or not names section should be encoded into the binary output. This enables a certain level of extra debug output in supported browser DevTools. Increases the size of the final binary. Default: false

filename

Filename of the compiled source code. Used in error outputs. Default: unknown.walt

extensions

An array of functions which are compiler extensions. See the Plugin section for plugin details. Default: []

note: Plugins are applied from right to left with the core language features applied last.

Plugin

The compiler may be extended via extensions or plugins. Each plugin must be a function return an object with the following keys: semantics, grammar. Where each value is a function.

type Plugin = (Options) => {
  semantics: ({ parser: Function, fragment: Function }) => {
    [string]: next => ([node: NodeType, context]) => NodeType
  },
  grammar: Function
}

Each plugin is capable of editing the following features of the compiler:

  • grammar - The syntax or grammar which is considered valid by the compiler. This enables features like new keywords for example.
  • semantics - The parsing of the ast. Each key in the object returned by this method is expected to be a middleware like parser function which may edit the node passed into it.

For an example of how plugins work see the full list of core language feature plugins.