Gleam 1.17 Adds 'gleam export escript' for Single-File BEAM Programs and a Create-Module Code Action
Gleam v1.17.0 bundles whole programs into a single escript runnable with only Erlang installed, and adds a language-server action that creates missing modules on import.
Overview
Gleam, the statically typed functional language that compiles to both the Erlang virtual machine and JavaScript, released version 1.17.0 on June 2, 2026, according to the project’s release announcement by project creator Louis Pilfold. The headline addition is a new gleam export escript command that bundles an entire program into a single file, alongside a language-server code action that generates missing modules and a set of optimizations to the JavaScript backend.
What We Know
The release centers on escript output. As the Gleam announcement describes it, “Much like a JavaScript bundle, an escript is a single file that contains all the modules of a program in the form of pre-compiled bytecode, and it can be run on any computer that has Erlang installed.” The changelog records the addition tersely: “The gleam export escript command has been added for the creation of escripts, BEAM programs bundled into a single file,” per the v1.17.0 CHANGELOG.
Running gleam export escript will “compile the project, verify it has a valid main function, and build the escript file from the compiled bytecode,” according to the release announcement. The resulting file is written into the project directory and can be executed directly. The feature gives BEAM-targeted Gleam programs a distribution format comparable to the single-file JavaScript bundles the language can already produce, requiring only an Erlang installation on the target machine rather than a full Gleam toolchain.
The second notable change is a language-server code action. The announcement describes it as “a new code action that may be especially appreciated by top-down programmers: create module,” adding that the action “is available any time that a module that does not exist is imported, and when run will create the missing module in the programmer’s package.” The changelog phrases the same feature as a code action “to create unknown modules when an import is added for a module that doesn’t exist.”
Version 1.17.0 also tightens the JavaScript code generator. The announcement summarizes the work as “detecting and removing some redundant checks when working with the length of bit arrays, and making the code for assignments more compact.” The changelog gives the precise rule: the compiler “now normalizes remaining-bytes bit-array checks for the JavaScript backend so (bitSize - c) % 8 === 0 becomes bitSize % 8 === 0 when the constant offset c is congruent modulo 8,” and notes that code generated for destructuring exhaustive patterns with let “is now less verbose on the JavaScript target.”
The build tool picked up smaller refinements. Per the changelog, gleam dev “now accepts the --no-print-progress flag,” gleam deps outdated “now always prints a summary showing how many packages have newer versions available,” gleam publish “will now better discover Git repository in monorepos,” and new projects are “created requesting Erlang/OTP version 29 on GitHub actions.” The final 1.17.0 changelog section also lists three hardening fixes, including restricting gleam docs build so it “cannot escape the docs output directory or project root” and restricting publication tarballs so “they cannot contain files from outside the project root,” according to the changelog.
The release follows the project’s incremental cadence. It arrived after two release candidates, with the v1.17.0-rc1 and v1.17.0-rc2 sections of the changelog dated 2026-05-23 and 2026-06-01 respectively. It is the project’s first feature release since Gleam 1.16, which previously shipped JavaScript source maps and parallel error reporting in April.
What We Don’t Know
The announcement does not quantify the size or startup characteristics of the generated escripts relative to other Gleam distribution formats, nor does it provide adoption or download figures for the release. The changelog lists no CVE identifiers for the three hardening fixes in the final 1.17.0 section, so the severity and disclosure history of those issues are not detailed in the cited material.
Analysis
The escript export closes a packaging gap that has distinguished Gleam’s two compilation targets. Programs built for JavaScript runtimes could already be emitted as a single bundle; BEAM programs now get an analogous one-file artifact that runs anywhere Erlang is present. For a language that markets itself as “a type safe and scalable language for the Erlang virtual machine and JavaScript runtimes,” per the announcement, bringing the two targets to parity on distribution is a practical step for command-line tools and scripts. Pilfold also reiterated the project’s independent posture in the same post, writing that “Gleam is not from big-tech and has not taken any VC funding” and that the project relies “entirely on the community.”