Feature: Add Elixir support (Wasm)

Abierto
  • ¿Algo no está bien?
#1,060 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
50/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
elixir, typescript, wasm
Área
web-dev

Línea de trabajo

Start with LiveCodes' adding-languages checklist, then study how ruby-wasm and python-wasm are wired: the compiler factory, the lang specification file, the result-page runtime script, and the vendors entry. The work is not yet green-lit — the thread is 5 comments deep on day one and asks the maintainer to confirm the Elixir/AtomVM subset target, and the issue author intends to implement it, so confirm claimability before starting. Done means a lang-elixir-wasm specification runs standard-library Elixir offline, plus starter template, docs, and end-to-end tests per the checklist.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

There is currently no option to run Elixir code in LiveCodes. I searched existing issues and found no open request for Elixir support.

Suggested feature

I propose adding Elixir as a script language, targeting the latest stable release (v1.20).

The implementation would follow the existing Wasm runtime pattern used by ruby-wasm and python-wasm:

  • Compiler factory as pass-through: async (code) => code
  • Runtime script loaded in the result page with scriptType: text/elixir-wasm
  • Runtime based on Popcorn / AtomVM, which compiles Elixir to WebAssembly and runs entirely offline in the browser. The public eval demo confirms client-side execution without a server.

Scope for the initial version would cover standard playground usage such as IO, Enum, pipes, and pattern matching. Full OTP features and frameworks such as Phoenix and LiveView would remain out of scope, consistent with AtomVM current subset limitations regarding file I/O, OS processes, and parts of the standard library.

Alternatives considered:

  • Hologram: full-stack framework on top of Phoenix, not suitable for plain Elixir support.
  • Server-side execution: rejected due to the client-side architecture requirement.

If the approach is approved, I will start with a proof of concept including lang-elixir-wasm specification, result page runner script, and vendors entry, then complete the remaining items from the adding-languages checklist including documentation, starter template, and end-to-end tests.

Please confirm whether the Elixir (Wasm) subset limitation is acceptable for the first version, or if a different compiler target is preferred.

Additional context

Lenguaje dominante
TypeScript
Estrellas
1.5k
Forks
267
Merge medio
7 h 47 min
PR fusionados (30 d)
14

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de live-codes/livecodes

Todos los issues de live-codes/livecodes

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.