gleam-lang/gleam

Path and Git dependencies for rebar3 packages

Open

#5,266 opened on Jan 6, 2026

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)Rust (960 forks)batch import
help wanted

Repository metrics

Stars
 (21,417 stars)
PR merge metrics
 (PR metrics pending)

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

Research direction
Investigate how non Hex Erlang packages are currently handled for Hex dependencies and extend that logic to path and git dependencies so that all three dependency types work uniformly.
Tech stack
rust
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70