gleam-lang/gleam

Path and Git dependencies for rebar3 packages

Open

#5,266 建立於 2026年1月6日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)Rust (21,417 star) (960 fork)batch import
help wanted

描述

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?

貢獻者指南

技術棧
rust
領域
build system
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Knowledge of Gleam's build systemFamiliarity with rebar3 and Hex
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
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.