
Research
/Security News
DuckDB npm Account Compromised in Continuing Supply Chain Attack
Ongoing npm supply chain attack spreads to DuckDB: multiple packages compromised with the same wallet-drainer malware.
walt-compiler
Advanced tools
This is the main walt compiler package.
npm install --save walt-compiler
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));
type Result = {
buffer: () => ArrayBuffer,
ast: NodeType,
semanticAST: NodeType
}
Unique (across function calls) ArrayBuffer
instance.
The Program
root node containing the source program without any type information. This is the node passed to semantic parser.
The Program
root node containing the source program including the final type information. This is the AST version used to generate the final binary.
type Options = {
version?: number,
encodeNames?: boolean,
filename?: string,
extensions: Array<Plugin>
}
The target WebAssembly Standard (not to be confused with compiler version) version to which the source should be compiled to. Currently supported versions: 0x01
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 of the compiled source code. Used in error outputs. Default: unknown.walt
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.
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.
FAQs
Alternative syntax for WebAssembly text format
We found that walt-compiler demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
Ongoing npm supply chain attack spreads to DuckDB: multiple packages compromised with the same wallet-drainer malware.
Security News
The MCP Steering Committee has launched the official MCP Registry in preview, a central hub for discovering and publishing MCP servers.
Product
Socket’s new Pull Request Stories give security teams clear visibility into dependency risks and outcomes across scanned pull requests.