gleam-lang/gleam

Hex Gleam dependency packages with colliding Erlang modules can fail to raise a compile error

Open

#4,657 opened on Jun 1, 2025

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Rust (960 forks)batch import
help wanted

Repository metrics

Stars
 (21,417 stars)
PR merge metrics
 (Avg merge 10d 19h) (69 merged PRs in 30d)

Description

sngrekov made a project with both Nibble and Glerray and started getting runtime errors. Both projects define the glearray_ffi Erlang module, and instead of raising an error at build time (as we should) we seem to let one clobber the other and as such one of the two packages will have the incorrect code.

Context: https://discord.com/channels/768594524158427167/1378738738376474634

Related: https://github.com/hayleigh-dot-dev/nibble/issues/24

Contributor guide

Research direction
Investigate the Gleam compiler's handling of Erlang module conflicts during dependency resolution. Look at the build system code to find where duplicate modules should be detected and raise a compile error.
Tech stack
rust
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGleam
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60