Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

wasmoon

Package Overview
Dependencies
Maintainers
1
Versions
53
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

wasmoon

A real lua VM with JS bindings made with webassembly

  • 1.3.0
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
451
decreased by-50%
Maintainers
1
Weekly downloads
 
Created
Source

Wasmoon

This package aims to provide a way to:

  • Embed Lua to any Node.js, Deno or Web Application.
  • Run lua code in any operational system

Installation

Globally via npm
$: npm install -g wasmoon

This will install wasmoon globally so that it may be run from the command line anywhere.

Running on-demand:

Using npx you can run the script without installing it first:

$: npx wasmoon

CLI Usage

Wasmoon by default reads and execute code from stdin, but you can force it to read from file passing the -f argument:

$: wasmoon -f file.lua

API Usage

To initialize, create a new Lua state, register the standard library, set a global variable, execute a code and get a global variable:

const { LuaFactory } = require('wasmoon')

// Initialize a new lua environment factory
// You can pass the wasm location as the first argument, useful if you are using wasmoon on a web environment and want to host the file by yourself
const factory = new LuaFactory();
// Create a standalone lua environment from the factory
const lua = await factory.createEngine();

try {
    // Set a JS function to be a global lua function
    lua.global.set('sum', (x, y) => x + y);
    // Run a lua string
    lua.doString(`
    print(sum(10, 10))
    function multiply(x, y)
        return x * y
    end
    `);
    // Get a global lua function as a JS function
    const multiply = lua.global.get('multiply');
    console.log(multiply(10, 10))
} finally {
    // Close the lua environment, so it can be freed
    lua.global.close();
}

Fixing common errors on web environment

Bundle/require errors can happen because wasmoon tries to safely import some node modules even in a browser environment, the bundler is not prepared to that since it tries to statically resolve everything on build time. Polyfilling these modules is not the right solution because they are not actually being used, you just have to ignore them:

Webpack

Add the resolve.fallback snippet to your config:

module.exports = {
    entry: './src/index.js', // Here is your entry file
    resolve: {
        fallback: {
            path: false,
            fs: false,
            child_process: false,
            crypto: false,
            url: false
        }
    }
};

Rollup

With the package rollup-plugin-ignore, add this snippet to your config:

export default {
    input: 'src/index.js', // Here is your entry file,
    plugins: [
        ignore(["path", "fs", "child_process", "crypto", "url"])
    ]
}

Angular

Add the section browser on package.json:

{
    "main": "src/index.js",
    "browser": {
        "child_process": false,
        "fs": false,
        "path": false,
        "crypto": false,
        "url": false
    }
}

Keywords

FAQs

Package last updated on 01 Apr 2021

Did you know?

Socket

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.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc