Skip to content

Consider adding runtime interpreters for all languages supported for browser js, nodejs, etc #220

Open
@ganeshkbhat

Description

Consider adding runtime interpreters for all languages supported for browser js, nodejs, and wasi.

  • Bug
  • [ x] Improvement
  • Other

Consider adding runtime interpretors for all languages supported for browser js, nodejs, and wasi. Currently I have following links you research and add https://www.npmjs.com/

  • "pyodide"
  • "micropython"
  • python-wasm
  • @cowasm/py-cython
  • @cowasm/py-pip , @cowasm/py-setuptools , @cowasm/python-pip
  • "ruby-head-wasm-wasi"
  • "ruby-head-wasm-emscripten"
  • "ruby-wasm-emscripten"
  • @cowasm/lua
  • @php-wasm/node , @php-wasm/web, @php-wasm/xxxx
  • php-wasm
  • @chriskoch/perl-wasm
  • @cgojin/rust-on-browser
  • @chriskoch/cpp-wasm
  • @tybys/cgen
  • @chriskoch/golang-wasm
  • @chriskoch/julia-wasm
  • @chriskoch/ocaml-wasm
  • @chriskoch/lld
  • webr [r-lang]
  • napi API - emnapi, napi-wasm
  • @napi-rs/wasm-runtime
  • https://github.com/ruby/ruby.wasm
  • non-wasm bridge - https://www.npmjs.com/package/java

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions