# Gleam

Gleam is a fast, friendly, and functional language for building type-safe, scalable systems!

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Gleam doesn't compile to Erlang source anymore

DevFeed: [Gleam doesn't compile to Erlang source anymore](<https://devfeed.tech/articles/gleam-doesn-t-compile-to-erlang-source-anymore-64919.md>)

Original publisher: [Read original article](<https://gleam.run/news/gleam-doesnt-compile-to-erlang-source-anymore>)

Author: Louis Pilfold

Published: 2026-10-05T00:00:00Z

Content type: release

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Compiler](<https://devfeed.tech/topics/compiler.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [Code generation](<https://devfeed.tech/topics/code-generation.md>), [Parsing](<https://devfeed.tech/topics/parsing.md>)

Tags: [beam](<https://devfeed.tech/tags/beam.md>), [build-times](<https://devfeed.tech/tags/build-times.md>), [code-generator](<https://devfeed.tech/tags/code-generator.md>), [code-quality](<https://devfeed.tech/tags/code-quality.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [debuggers](<https://devfeed.tech/tags/debuggers.md>), [encoding](<https://devfeed.tech/tags/encoding.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [gleam](<https://devfeed.tech/tags/gleam.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [performance](<https://devfeed.tech/tags/performance.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [source-code](<https://devfeed.tech/tags/source-code.md>), [syntax](<https://devfeed.tech/tags/syntax.md>), [type-safe](<https://devfeed.tech/tags/type-safe.md>), [virtual-machine](<https://devfeed.tech/tags/virtual-machine.md>)

### AI overview

Gleam v1.19.0 rewrites its Erlang code generator to emit Erlang abstract forms, which the Erlang compiler can load directly, skipping its tokenizer and parser. The article reports faster Erlang builds and runtime location metadata that points accurately to Gleam source, improving crash reports and stack traces; debugger support such as edb is described as a possibility, not completed work. It favors abstract forms over direct BEAM bytecode because bytecode changes across VM releases, and reproducing Erlang compiler optimizations would take substantial ongoing effort. The release also flattens generated JavaScript for pattern matches, improves short-list construction while retaining array conversion for longer lists, preserves TypeScript generic types through overloads, adds build-tool support including generated `.app` files and a `--no-dev` flag, and adds language-server label operations, browser formatting capability, and more targeted errors. Its compilation benchmark compares a small synthetic workload and is explicitly limited; it cannot establish performance across real projects.

### Source excerpt

Gleam is a type-safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Today Gleam v1.19.0 has been published, so let's go over what's new. A new compilation target Over the last few months Giacomo Cavalieri has entirely rewritten Gleam's Erlang code generator that has an entirely different design, and most notably, outputs a different format. Previously Gleam generated Erlang source code, now it generates Erlang abstract forms. "Erlang abstract forms" is an intermediate representation used by the Erlang compiler. It is a metadata-annotated tree that represents Erlang syntax, and it is normally produced by running Erlang's tokeniser and parser. It has a binary encoding using Erlang's external term format, and with this binary format we can load our generated code directly, skipping the front-half of the Erlang compiler. This new Erlang code generator brings several benefits: The performance of the compiler has been improved, significantly reducing the build times for Gleam projects running on Erlang. The location metadata available to the runtime is now accurate to original Gleam source code, rather than to the Erlang source code the compiler would generate. This means, for example, the line numbers in BEAM crash reports and stacktraces are perfectly accurate, while previously they could be inaccurate, only pointing to the nearest function. This metadata could also enable full support for Gleam in debuggers such as edb, though we have not done any work on this ourselves. The code-quality of the Gleam compiler has been improved. The Erlang code generator was one of the oldest and most stable parts of the Gleam codebase, so while it wasn't causing us any problems it wasn't conforming to the standards and conventions we have today. This new replacement is excellent, and arguably raising the bar for the compiler as whole. We never have to hear someone use the word "transpiler" as a pejorative ever again.1 Ok, so how fast is it? I'm going to s

## Gleam Gathering 2027 is coming to London!

DevFeed: [Gleam Gathering 2027 is coming to London!](<https://devfeed.tech/articles/gleam-gathering-2027-is-coming-to-london-51505.md>)

Original publisher: [Read original article](<https://gleam.run/news/gleam-gathering-2027-is-coming-to-london>)

Author: Kamila Pokój

Published: 2026-09-11T00:00:00Z

Content type: news

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [SINGAJUG](<https://devfeed.tech/topics/singajug.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [arcade-games](<https://devfeed.tech/tags/arcade-games.md>), [community](<https://devfeed.tech/tags/community.md>), [conference](<https://devfeed.tech/tags/conference.md>), [gathering](<https://devfeed.tech/tags/gathering.md>), [gleam](<https://devfeed.tech/tags/gleam.md>), [library](<https://devfeed.tech/tags/library.md>), [london](<https://devfeed.tech/tags/london.md>), [talks](<https://devfeed.tech/tags/talks.md>), [tickets](<https://devfeed.tech/tags/tickets.md>)

### AI overview

Gleam Gathering 2027 is being prepared for London, with tickets available and its call for talks open. The announcement invites proposals about Gleam projects, lessons, libraries, tools, or other topics the community may enjoy. It also notes that recordings of the 2026 talks have been released for those who missed the Bristol event.

### Source excerpt

Earlier this year we had a fantastic time at the first ever 100% Gleam conference. Gleam Gathering was a blast and it was incredible to see so many Gleamlins in one place. There were talks from community members and Gleam core team members, plenty of interesting conversations about Gleam, other tech and just life in general. And all the side fun like bouldering, pizza and arcade games. If you couldn't make it to Bristol, all the 2026 talks have been released, so you can see for yourself what the event was all about. Now many of us are already preparing for Gleam Gathering 2027. Tickets are already available and the call for talks is open. If you've been working on something interesting with Gleam, learned something worth sharing, built a library or tool, or simply have a topic you think other Gleamlins would enjoy hearing about, make sure to send your proposal!! See you there!

## Help from the Github Security Lab

DevFeed: [Help from the Github Security Lab](<https://devfeed.tech/articles/help-from-the-github-security-lab-51506.md>)

Original publisher: [Read original article](<https://gleam.run/news/help-from-the-github-security-lab>)

Author: Louis Pilfold

Published: 2026-08-17T00:00:00Z

Content type: opinion

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [open source maintenance](<https://devfeed.tech/topics/open-source-maintenance.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [collaboration](<https://devfeed.tech/tags/collaboration.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [github](<https://devfeed.tech/tags/github.md>), [github-security](<https://devfeed.tech/tags/github-security.md>), [github-security-lab](<https://devfeed.tech/tags/github-security-lab.md>), [gleam](<https://devfeed.tech/tags/gleam.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [secure-open-source](<https://devfeed.tech/tags/secure-open-source.md>), [security](<https://devfeed.tech/tags/security.md>), [security-education](<https://devfeed.tech/tags/security-education.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>), [skills](<https://devfeed.tech/tags/skills.md>), [sponsorship](<https://devfeed.tech/tags/sponsorship.md>), [team](<https://devfeed.tech/tags/team.md>), [training](<https://devfeed.tech/tags/training.md>)

### AI overview

Gleam's participation in GitHub's Secure Open Source Fund brought training, a year of security improvements, and expert review. The team says it uncovered no vulnerabilities or gaps in Gleam's existing security processes, but guidance from GitHub Security Lab and the Erlang Ecosystem Foundation helped validate decisions and surface unknowns. The author also stresses that security depends on communicating evidence: policies, documentation, and compliance frameworks can help users assess and trust a project. Since many dependencies lack time, expertise, and funding, supporting their security is presented as a cost-effective way to reduce risks across the software ecosystem.

### Source excerpt

Earlier in the year, Gleam was invited to and participated in the 4th GitHub Secure Open Source Fund, an annual program that supports key open source projects in order to secure the open source ecosystem as a whole. It consists of a 3-week security training program1, a 12-month engagement in which ongoing security improvements are implemented, and $10,000 USD of GitHub Sponsorship. All incredibly valuable to the Gleam project, and what an honour to be selected! We've made numerous security improvements off the back of the program, and have more yet planned, but they would either make rather dry reading or deserve their own release announcement, so I won't bore you with the details here. Instead, here are my main takeaways from the program so far. Gleam is ahead of the pack in terms of security I'm delighted to say that the Gleam project was in an excellent position in terms of security before the program even began. Thanks to the hard work of the Gleam team and contributors, and our collaboration with The Erlang Ecosystem Foundation (aka the EEF), we were able to slap a metaphorical #already-implemented tag on many of the items that other projects would have to add to their development backlog. We did not uncover any security vulnerabilities or ways in which our security processes were lacking. Excellent news! Does that mean that this aspect of the security education was not helpful? Not at all, it was still greatly impactful because... Experts know what you don't know In the Gleam team we care deeply about security, and it is at the front of my mind any time we develop anything, from compiler improvements, to language design, to libraries, to documentation. The security of the Gleam ecosystem and Gleam programmers is non-negotiable. That said, we are not primarily security experts2. We have security skills and knowledge, but our real strengths lie in language design, compiler and application development, ecosystem construction, and community management. When making c

## A field day for Gleam's language server

DevFeed: [A field day for Gleam's language server](<https://devfeed.tech/articles/a-field-day-for-gleam-s-language-server-51503.md>)

Original publisher: [Read original article](<https://gleam.run/news/a-field-day-for-gleams-language-server>)

Author: Louis Pilfold

Published: 2026-07-29T00:00:00Z

Content type: release

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Release notes](<https://devfeed.tech/topics/release-notes.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [modules](<https://devfeed.tech/topics/modules.md>), [conditionals](<https://devfeed.tech/topics/conditionals.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [field](<https://devfeed.tech/tags/field.md>), [fields](<https://devfeed.tech/tags/fields.md>), [gleam](<https://devfeed.tech/tags/gleam.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [language](<https://devfeed.tech/tags/language.md>), [modules](<https://devfeed.tech/tags/modules.md>), [server](<https://devfeed.tech/tags/server.md>), [type](<https://devfeed.tech/tags/type.md>), [variables](<https://devfeed.tech/tags/variables.md>)

### AI overview

Gleam v1.18.0 adds broad language-server support for record-field navigation, references, and renaming across modules, plus renaming of type variables and modules, a pattern-match code action for function calls, and several other editing actions. The JavaScript compiler now reuses a single value for data structures whose instances are equivalent; tests report performance gains, especially in Lustre view functions. Compiler and formatter work using memory arenas made `gleam format` up to 13% faster on Lustre projects with 10% lower peak memory, and remains ongoing. The release also deprecates an ambiguous pipe form, with a code action to rewrite it explicitly; adds a subdirectory `path` option for Git dependencies; and accepts a read-only Hex API key through `HEXPM_READ_API_KEY` to access higher rate limits. Hex error messages, documentation URLs, and owner commands also received updates.

### Source excerpt

Gleam is a type safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Today Gleam v1.18.0 has been published. Language server record field support Gleam's focus on static analysis and static types really helps with creating tooling, and that can be seen very clearly with Gleam's much-loved language server. All its features and capabilities can be seen in its documentation. One remaining missing part of it was full support for record fields, a problem now fixed! The language server now supports go-to-definition, find-references and rename for record fields. These work on the field declaration, on labelled arguments, on labelled patterns, on record updates and on record.field accesses, both within a module and across modules. For example: pub type Person { Person(name: String, age: Int) } pub fn main() { let lucy = Person(name: "Lucy", age: 10) lucy.name // ^ Go-to-definition jumps to the `name` field, and renaming it here // renames the field everywhere it is used. } Thank you Alistair Smith! People will be very happy for this one! Type variable renaming Similarly, the language server now permits renaming type variables in functions, types, and constants. For example: pub fn twice(value: a, f: fn(a) -> a) -> a { // ^ Rename to "anything" f(f(value)) } Produces: pub fn twice(value: anything, f: fn(anything) -> anything) -> anything { f(f(value)) } Thank you Surya Rose! Updating imports for renamed modules Another addition to the language server is support for renaming modules. When your text editor tells the language server that a Gleam file has been renamed, it will find all the uses of that module and update them for the new name. For example: import db_users pub fn main() -> db_users.User { db_users.new("username") } Renaming db_users.gleam to database/user.gleam would produce: import database/user pub fn main() -> user.User { user.new("username") } Thank you Surya Rose! Pattern match on value code action Flow control in Gleam is done w

## Single file Gleam BEAM programs with escript

DevFeed: [Single file Gleam BEAM programs with escript](<https://devfeed.tech/articles/single-file-gleam-beam-programs-with-escript-51510.md>)

Original publisher: [Read original article](<https://gleam.run/news/single-file-gleam-beam-programs-with-escript>)

Author: Louis Pilfold

Published: 2026-06-02T00:00:00Z

Content type: release

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Erlang](<https://devfeed.tech/topics/erlang.md>), [Build tool](<https://devfeed.tech/topics/build-tool.md>), [modules](<https://devfeed.tech/topics/modules.md>), [Compilers and Linkers](<https://devfeed.tech/topics/compilers-and-linkers.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Bun](<https://devfeed.tech/topics/bun.md>)

Tags: [beam](<https://devfeed.tech/tags/beam.md>), [bytecode](<https://devfeed.tech/tags/bytecode.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [file](<https://devfeed.tech/tags/file.md>), [gleam](<https://devfeed.tech/tags/gleam.md>), [modules](<https://devfeed.tech/tags/modules.md>), [v1](<https://devfeed.tech/tags/v1.md>)

### AI overview

Gleam v1.17.0 adds `gleam export escript` for BEAM projects: it compiles the project, checks for a valid `main` function, and packages compiled modules into one executable file for computers with Erlang installed. The release also adds language-server highlighting for variable references, permits `todo` in constants so incomplete code can still be type checked, and improves editor actions and compiler suggestions. Other changes include quieter `gleam dev` output, an outdated-dependency count, better Git detection when publishing from a monorepo, JavaScript pattern-matching optimizations, and fixes for configuration-validation vulnerabilities. The supplied text also describes improved record hovers and code actions for record updates, patterns, operators, and missing modules.

### Source excerpt

Gleam is a type safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Today Gleam v1.17.0 has been published. Gleam Gathering But first: the first videos from the first ever all-Gleam conference have been released! You can view them on the Gleam Gathering YouTube account. The event was a roaring success and loads of fun. Stay tuned for news of the next one in 2027! Right, back to the release coverage. BEAM escripts When running on the Erlang virtual machine Gleam code is compiled to a series of .beam files, each of which contains the bytecode for a single Gleam module. This works fine for programs distributed or installed using package managers, containers, or other such systems, but having many files to share is a little inconvenient for sharing small command-line programs. In the JavaScript world this problem is solved using a "bundler", a program that takes many JavaScript modules and combines them into a single file. This single file can be copied to and run on any computer that has a JavaScript runtime installed (such as NodeJS, Deno, or Bun). Erlang has a similar solution: escripts. 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 Erlang build tool has a convenient command for creating an escript, but for Gleam programmers the escript creation process has not been as straightforward. This release brings the gleam export escript command, which will compile the project, verify it has a valid main function, and build the escript file from the compiled bytecode. louis ~/src/my_project $ gleam export escript Compiling gleam_stdlib Compiling my_project Compiled in 0.48s Your escript has been generated to /home/louis/src/my_project/my_project. louis ~/src/my_project $ ./my_project Hello from my_project! Highlight references Gleam's language server provides IDE functionality for all edi

## JavaScript source maps

DevFeed: [JavaScript source maps](<https://devfeed.tech/articles/javascript-source-maps-51507.md>)

Original publisher: [Read original article](<https://gleam.run/news/javascript-source-maps>)

Author: Louis Pilfold

Published: 2026-04-24T00:00:00Z

Content type: release

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Compilers and Linkers](<https://devfeed.tech/topics/compilers-and-linkers.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [typesafety](<https://devfeed.tech/topics/typesafety.md>), [Build tool](<https://devfeed.tech/topics/build-tool.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Transpilers](<https://devfeed.tech/topics/transpilers.md>), [IntelliJ IDEA](<https://devfeed.tech/topics/intellij-idea.md>)

Tags: [breakpoint](<https://devfeed.tech/tags/breakpoint.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [debug](<https://devfeed.tech/tags/debug.md>), [debuggers](<https://devfeed.tech/tags/debuggers.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [dev-tools](<https://devfeed.tech/tags/dev-tools.md>), [exception](<https://devfeed.tech/tags/exception.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [maps](<https://devfeed.tech/tags/maps.md>), [safari](<https://devfeed.tech/tags/safari.md>), [source](<https://devfeed.tech/tags/source.md>)

### AI overview

Gleam v1.16.0 adds JavaScript source maps so browser tools can show original Gleam locations in code, stack traces, and debugging sessions; enable them with `javascript.source_maps = true` and serve the generated map files. Serving the build directory or using Lustre's dev-tools already handles that. The release also improves language-server fault tolerance by reporting imports that lead to compilation failures and continuing with compilable module branches. Other changes include nearly 30% faster single-character string-prefix matching in the cited `glance` benchmark, a warning for JavaScript integer patterns wider than its 52-bit precision limit, package owner management, and additional code actions and compiler improvements.

### Source excerpt

Gleam is a type safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Today Gleam v1.16.0 has been published, let's go over what's new. Gleam gets source maps Gleam's robust type system makes runtime errors very rare, but it would be naive to say that it's never necessary to debug Gleam code at runtime. When compiling code to JavaScript one challenge for runtime debugging is that the error and the source code shown is that of the compiled JavaScript, not the Gleam the programmer actually wrote. The solution to this problem is source maps, additional files that Gleam's compiler can now generate, teaching browsers and JavaScript runtimes what the original code is and how it maps on to the JavaScript it runs. Here it is in action with Safari's dev-tools: As you may know, it's not limited to just displaying the code, it also translates exception stack traces to the original locations, and enables use of breakpoints and debuggers. To enable source maps set the javascript.source_maps property to true in your gleam.toml, and ensure that you are serving these new files to the web browser along with your JavaScript code. If you are serving the build directory or using Lustre's dev-tools then there's nothing else to do. name = "my_project" version = "1.0.0" [javascript] source_maps = true [dependencies] gleam_stdlib = ">= 1.0.0 and < 2.0.0" A huge thank you to Ameen Radwan for this big improvement. Folks who enjoy breakpoint debugging will be especially pleased. Package-level fault tolerance Gleam is a fully-typed language, so to compile a module of Gleam code the compiler must first successfully compile all the modules it imports in order to have the required type information. Attempting to analyse modules without this information would result in a cascading failure of incorrect and misleading error messages, so when a module cannot be compiled the build tool stops and reports the errors. This behaviour successfully prevents the error cascade, bu

## Upgrading Hex security

DevFeed: [Upgrading Hex security](<https://devfeed.tech/articles/upgrading-hex-security-51512.md>)

Original publisher: [Read original article](<https://gleam.run/news/upgrading-hex-security>)

Author: Louis Pilfold

Published: 2026-03-16T00:00:00Z

Content type: release

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [MFA](<https://devfeed.tech/topics/mfa.md>), [Package Management](<https://devfeed.tech/topics/package-management.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [gleam](<https://devfeed.tech/tags/gleam.md>), [hex](<https://devfeed.tech/tags/hex.md>), [identity-management](<https://devfeed.tech/tags/identity-management.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [multi-factor-authentication](<https://devfeed.tech/tags/multi-factor-authentication.md>), [oauth2](<https://devfeed.tech/tags/oauth2.md>), [password](<https://devfeed.tech/tags/password.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [providers](<https://devfeed.tech/tags/providers.md>), [security](<https://devfeed.tech/tags/security.md>), [stolen-credentials](<https://devfeed.tech/tags/stolen-credentials.md>)

### AI overview

Gleam v1.15.0 switches Hex authentication exclusively to OAuth2: write actions require multi-factor authentication, clients no longer handle passwords, tokens expire quickly, and Hex can use external OAuth providers. On first Hex use, the new Gleam version revokes locally stored legacy tokens; legacy authentication for Gleam packages is slated for future deactivation. Passwords encrypting local Hex tokens must be at least eight characters. The release also improves Hex error messages, guard expressions, JavaScript FFI and generated TypeScript types, and language-server features such as folding, renaming and more precise completions. Publishing now rejects packages with no README or the default generated README. Configuration keys `dev-dependencies` and `tag-prefix` are moving to snake_case; old spellings remain supported but are deprecated. The supplied text also describes CLI documentation and code-action improvements.

### Source excerpt

Gleam is a type safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Today Gleam v1.15.0 has been published, let's go over what's new. The Hex package manager Gleam is a BEAM language, so it uses Hex, the package manager of the Erlang ecosystem. Hex recently introduced a new OAuth2 based authentication system, replacing the old system of exchanging the account's username and password for a long-lived token. This new system has many security advantages: Multi-factor authentication is used for all endpoints that require write permissions, so stolen credentials or tokens are insufficient to perform sensitive actions. Hex clients such as Gleam never see your password, so there is less opportunity for an attacker to harvest credentials given access to your workstation. The access tokens are short lived, so if stolen there is only a small window in which they could be used by the attacker. The Hex site can integrate with other OAuth providers, enabling companies to use their existing identity management and audit systems to secure Hex. Gleam now uses exclusively this new system for authentication, and any existing legacy tokens that Gleam has stored locally will be revoked the first time that the new version of Gleam is used with Hex. The legacy system will be disabled for Gleam packages in future. Lastly, the password used for encrypting local Hex tokens must now be at least 8 characters in length. This work was done in collaboration with The Erlang Ecosystem Foundation. A huge thank-you to Jonatan Männchen and the rest of the team there! If you would like to support important infrastructure projects for the whole ecosystem consider becoming a member of the foundation. Better Hex errors It's possible for Hex operations to fail, for example, attempting to depend on a package that does not exist, or attempting to publish a new version of a package that you are not the maintainer of. When this happens we typically show the programmer the error

## Join us at Gleam Gathering

DevFeed: [Join us at Gleam Gathering](<https://devfeed.tech/articles/join-us-at-gleam-gathering-51508.md>)

Original publisher: [Read original article](<https://gleam.run/news/join-us-at-gleam-gathering>)

Author: Louis Pilfold

Published: 2026-02-11T00:00:00Z

Content type: news

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Developer Events](<https://devfeed.tech/topics/developer-events.md>)

Tags: [arcade](<https://devfeed.tech/tags/arcade.md>), [community](<https://devfeed.tech/tags/community.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [conference](<https://devfeed.tech/tags/conference.md>), [gathering](<https://devfeed.tech/tags/gathering.md>), [gleam](<https://devfeed.tech/tags/gleam.md>), [join](<https://devfeed.tech/tags/join.md>), [retro-games](<https://devfeed.tech/tags/retro-games.md>), [talks](<https://devfeed.tech/tags/talks.md>)

### AI overview

Gleam Gathering is a community conference taking place in Bristol, UK, on February 21, described as the first conference devoted entirely to Gleam. Talks by community members and core team members will cover topics from compiler optimisation to trains. The event also offers time to meet other attendees, followed by a visit to a retro-games arcade; the author mentions a possible visit to a local climbing gym the next day. The text says a few last-minute tickets remain.

### Source excerpt

Gleam Gathering is right around the corner! On the 21st of February the Gleam team and many friendly Gleamlins will be meeting in Bristol UK for the first ever 100% Gleam conference. This is a milestone for the community, and we are very excited. There will be talks from community members and Gleam core team members on topics ranging from compiler optimisation to trains (seemingly a popular subject within the Gleam community). Around the presentations there's opportunity to meet and talk with folks from the community, and afterwards we will be going to a retro-games arcade for some fun. I may check out the local rock-climbing gym the day after too! If you'd like to join us then there's a few last minute tickets remaining. See you in Bristol!

## The happy holidays release 2025 🎁

DevFeed: [The happy holidays release 2025 🎁](<https://devfeed.tech/articles/the-happy-holidays-release-2025-51511.md>)

Original publisher: [Read original article](<https://gleam.run/news/the-happy-holidays-2025-release>)

Author: Louis Pilfold

Published: 2025-12-25T00:00:00Z

Content type: release

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Functional programming](<https://devfeed.tech/topics/functional-programming.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [export](<https://devfeed.tech/topics/export.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [annotation](<https://devfeed.tech/tags/annotation.md>), [annotations](<https://devfeed.tech/tags/annotations.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [ecosystems](<https://devfeed.tech/tags/ecosystems.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [external](<https://devfeed.tech/tags/external.md>), [holidays](<https://devfeed.tech/tags/holidays.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [language](<https://devfeed.tech/tags/language.md>), [release](<https://devfeed.tech/tags/release.md>), [runtimes](<https://devfeed.tech/tags/runtimes.md>), [static-analysis](<https://devfeed.tech/tags/static-analysis.md>), [type-safe](<https://devfeed.tech/tags/type-safe.md>), [types](<https://devfeed.tech/tags/types.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [v1](<https://devfeed.tech/tags/v1.md>)

### AI overview

Gleam v1.14.0 improves interoperability, compiler analysis, and developer tooling across Erlang, JavaScript, and the BEAM ecosystem. External types can now use `@external` annotations to generate precise Erlang and TypeScript definitions instead of vague `any` types. Pattern analysis adds interference based pruning for integer segments and canonical number normalization, helping optimize matches and detect unreachable clauses. The compiler also improves error locations and recovery from errors, warns about empty modules and detached documentation, and supports record updates in constants. JavaScript equality checks for fieldless custom variants are faster. Language server updates include type ranked autocomplete, broader refactoring actions, more useful diagnostics, and annotation generation for all top level definitions. Build tool additions include `gleam deps outdated`, clearer missing Git errors, updated Elixir compiler API support, and CLI refinements.

### Source excerpt

Merry Christmas and happy holidays everyone! Gleam is a type-safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Gleam v1.14.0 is our Xmas gift for you, let's unwrap it and take a look inside. External annotations for external types Gleam doesn't exist in a vacuum, instead builds upon the existing Erlang and JavaScript ecosystems. It's not uncommon for Gleam programs and libraries to internally make use of code written in other languages in the same ecosystem, and Gleam code can be called from those languages too. To help with the interoperability between these languages the Gleam compiler can generate Erlang type specifications and TypeScript declaration files. These can be used with external type checkers and static analysis tooling to ensure the various languages are calling each other's code correctly. // Function written in Gleam pub fn greet(name: String) -> String { "Hello, " <> name <> "!" } % Generated Erlang type spec -spec greet(binary()) -> binary(). // Generated TypeScript type definition export function greet(name: string): string; When writing bindings to code in other languages, Gleam's external type feature is used to declare a type that can be referenced in Gleam, but since it originates from outside of Gleam it has an unknown shape and cannot be constructed directly. A very useful feature for designing Gleam-y APIs for external code! The limitation here was that due to Gleam not knowing anything about these external types, it was not able to produce a precise definition in generated Erlang or TypeScript type definitions, having to fall back to the correct but vague "any" type of each language. The @external annotation is now supported for external types, giving the programmer a way to specify an Erlang or TypeScript type definition to be used. For example, the Dict type from the standard library can now be written as the following: // External type declared in Gleam @external(erlang, "erlang", "map") @external(javasc

## Formalising external APIs

DevFeed: [Formalising external APIs](<https://devfeed.tech/articles/formalising-external-apis-51504.md>)

Original publisher: [Read original article](<https://gleam.run/news/formalising-external-apis>)

Author: Louis Pilfold

Published: 2025-10-19T00:00:00Z

Content type: release

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Tool](<https://devfeed.tech/topics/tool.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [conditionals](<https://devfeed.tech/topics/conditionals.md>), [adapter pattern](<https://devfeed.tech/topics/adapter-pattern.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>), [code beautification](<https://devfeed.tech/topics/code-beautification.md>), [import](<https://devfeed.tech/topics/import.md>), [modules](<https://devfeed.tech/topics/modules.md>), [Sequences](<https://devfeed.tech/topics/sequences.md>), [Functional programming](<https://devfeed.tech/topics/functional-programming.md>), [identifier](<https://devfeed.tech/topics/identifier.md>), [Exception handling](<https://devfeed.tech/topics/exception-handling.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [beam](<https://devfeed.tech/tags/beam.md>), [data](<https://devfeed.tech/tags/data.md>), [data-types](<https://devfeed.tech/tags/data-types.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [ecosystems](<https://devfeed.tech/tags/ecosystems.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [external](<https://devfeed.tech/tags/external.md>), [interface](<https://devfeed.tech/tags/interface.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [performance](<https://devfeed.tech/tags/performance.md>), [wrapper](<https://devfeed.tech/tags/wrapper.md>)

### AI overview

Gleam v1.13.0 adds a documented guide for externals and a dedicated JavaScript API for constructing and inspecting Gleam data. Existing JavaScript externals will need to migrate, with tooling and team help planned. The compiler also prunes redundant bit-array checks and warns about impossible bit patterns, unused recursive arguments, and inefficient list-length emptiness checks. Build output now reports dependency changes to support auditing locked versions. Many language-server improvements add or refine code actions, including extracting functions, expanding and collapsing pattern matches, and generating functions across modules; extraction uses a placeholder name because of an LSP limitation. Other changes improve type names in generated documentation and editor actions, syntax diagnostics, and formatter behavior.

### Source excerpt

Gleam is a type-safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Today Gleam v1.13.0 has been published. Let's go over all the highlights now. External API for Gleam data One of Gleam's strengths is that it is part of the BEAM and JavaScript ecosystems, enabling Gleam programs to take advantage of code written in Erlang, Elixir, JavaScript, and more. This is a large part of how Gleam was able to become a practical production-ready language so quickly, by not restricting Gleam programmers to just the comparatively young Gleam package ecosystem. A function written in one of these other languages can be imported into a Gleam module as an "external function", and then called without any additional performance overhead. @external(erlang, "moon_base", "launch_spaceship") pub fn lift_off(countdown: Int) -> Result(Spaceship, LaunchError) Here the Erlang function launch_spaceship from the module moon_base is being imported. One restriction to external functions is that they will need to return data types that Gleam can understand. Gleam's "external type" feature lets the programmer refer to types defined in other languages, but if the programmer wants to be able to directly construct and pattern match data from external functions it will need to be in a format compatible with Gleam data types. Often a programmer will write a small wrapper function in the external language to convert the data, and also to make the interface adhere to Gleam patterns and conventions. -module(moon_base). -export([launch_spaceship/1]). launch_spaceship(Countdown) -> try Spaceship = launch_control:launch_spaceship(Countdown), {ok, Spaceship} catch error:no_fuel -> {error, no_fuel}; error:bad_weather -> {error, bad_weather} end. This launch_spaceship Erlang function wraps the function from the launch_control module, converting the exception-based API into a Result type, the Erlang representation of Gleam's Ok and Error variants. One thing that a Gleam programmer ma

## No more dependency management headaches

DevFeed: [No more dependency management headaches](<https://devfeed.tech/articles/no-more-dependency-management-headaches-51509.md>)

Original publisher: [Read original article](<https://gleam.run/news/no-more-dependency-management-headaches>)

Author: Louis Pilfold

Published: 2025-08-05T00:00:00Z

Content type: release

Language: en

Sources: [Gleam](<https://devfeed.tech/sources/gleam.md>)

Topics: [Dependency management](<https://devfeed.tech/topics/dependency-management.md>), [Package Management](<https://devfeed.tech/topics/package-management.md>), [Algorithms](<https://devfeed.tech/topics/algorithms.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>)

Tags: [dependency](<https://devfeed.tech/tags/dependency.md>), [dependency-management](<https://devfeed.tech/tags/dependency-management.md>), [error](<https://devfeed.tech/tags/error.md>), [error-messages](<https://devfeed.tech/tags/error-messages.md>), [javascript](<https://devfeed.tech/tags/javascript.md>)

### AI overview

Gleam v1.12.0 makes dependency conflicts easier to resolve by showing the package version requirements that clash, and `gleam update` and `gleam deps download` now report when newer major versions are available. Major upgrades may include breaking changes, so developers still need to check compatibility. Other changes include custom messages for `echo`, smaller generated output, more flexible list formatting, and JSDoc comments in JavaScript output. Compiler diagnostics add hints for discarded variables and redundant comparisons; the release also enables conservative Erlang local-function inlining, which may improve performance for some BEAM programs.

### Source excerpt

Gleam is a type-safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Today Gleam v1.12.0 has been published. Let's take a look at the highlights. Understanding dependency conflicts Gleam packages use semantic versioning, and they specify what ranges of releases they are compatible with to ensure that all selected versions are compatible with each other. This is very useful in ensuring that you don't end up stuck with invalid versions that cause the project to fail to compile, or are broken in more confusing subtle ways. This does, however, mean that sometimes you will have conflicts when adding a dependency, as there's no version which is compatible with the existing versions you have locked. Historically this has been very confusing as we haven't been able to display much useful information when this happens. error: Dependency resolution failed An error occurred while determining what dependency packages and versions should be downloaded. The error from the version resolver library was: Unable to find compatible versions for the version constraints in your gleam.toml. The conflicting packages are: - app - wisp - mist - gleam_otp - gleam_json It's not clear at all what the problem is, or what the programmer might need to do to resolve the problem. This is not fun for them at all. Thanks to a lot of hard work from Jak and a new release of the underlying pubgrub version solving algorithm library Gleam will now provide much clearer error messages: error: Dependency resolution failed There's no compatible version of `gleam_otp`: - You require wisp >= 1.0.0 and < 2.0.0 - wisp requires mist >= 1.2.0 and < 5.0.0 - mist requires gleam_otp >= 0.9.0 and < 1.0.0 - You require lustre >= 5.2.1 and < 6.0.0 - lustre requires gleam_otp >= 1.0.0 and < 2.0.0 There's no compatible version of `gleam_json`: - You require wisp >= 1.0.0 and < 2.0.0 - wisp requires gleam_json >= 3.0.0 and < 4.0.0 - You require gleam_json >= 2.3.0 and < 3.0.0 Version solving is