gleam-lang/gleam

Path and Git dependencies for rebar3 packages

Open

#5266 opened on Jan 6, 2026

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Rust (21,417 stars) (960 forks)batch import
help wanted

Description

I have an Erlang package that I wish to test linked to a Gleam project, but this Erlang package is not published on Hex. If this was a Gleam package, I would be able to include it using my_package = { path = "../my-package" } but I it seems when such a package does not contain gleam.toml, it is considered invalid.

Whatever logic that is used to make a non-Gleam package from Hex work, could that be applied to a non-Gleam package from path or git dependencies so all three work the same way?

Contributor guide

Tech stack
rust
Domain
build system
Issue type
feature
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Knowledge of Gleam's build systemFamiliarity with rebar3 and Hex
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate how Gleam currently handles non Gleam packages from Hex (likely in the hex module). Look for the logic that validates packages without gleam.toml and adapt it for path and git dependencies. Relevant files may be in src/gleam/hex.rs or similar. Check comments for any maintainer guidance on desired behavior.