Papipo

Papipo

Request for testers: Gleam support in Mix

Hi!

I have a PR on the elixir repo that adds support for gleam in Mix.

There you’ll find the instructions to test the feature before it’s released. It will allow you to add gleam path dependencies in your mix.exs file without the need for the mix_gleam archive.

Please try it out and report back with your findings, if any.

Thanks,
Rodrigo.

First 10 of 28 Posts Switch mode

lostbean

lostbean

Thanks for working on this PR Rodrigo! It’s coming in at a perfect timing :smiley:

Today I was trying to set up a new umbrella repo and import an external Gleam project. I had started with gleam_mix but was clearly having issues given my umbrella + external Gleam project setup. Then I found this post and I’m super grateful for the help to get this working.

I just compiled your branch (I’m using Nix with src overlay) and rewound the gleam_mix config. At first I got this error:

12:19:03.397 [error] beam/beam_load.c(583): Error loading function ‘Elixir.Hex.Netrc.Cache’:fetch/1: op make_fun2 u: please re-compile this module with an Erlang/OTP 27 compiler or update your Erlang/OTP version

That was easy to fix by wiping out project and home folder caches (e.g. rm -rf ~/.mix).

Now when I run mix deps.get, I’m getting this:

zsh ❯ mix deps.get
error: unrecognized subcommand 'package-information'

  tip: a similar subcommand exists: 'package-interface'

Usage: gleam export <COMMAND>

For more information, try '--help'.
** (Mix) Command "gleam export package-information --out /dev/stdout" failed with reason:

I believe that is because I’m running on Gleam 1.9.1. Should it be using the ‘package-interface’ given this is the newest version?

Papipo

Papipo OP

I believe that is because I’m running on Gleam 1.9.1. Should it be using the ‘package-interface’ given this is the newest version?

No, export package-information is a new command I had to implement in the gleam compiler precisely for Mix integration: it exports the gleam.toml file as JSON so Mix can use it.

As described on the PR comment you need to install gleam nightly to have this new command, which will be released in gleam 1.10.0. That should fix the issue you are having.

Let me know if you hit any other hurdle after that or if it works as expected. Thanks!

lostbean

lostbean

Amazing! Just using the latest main branch from Gleam and mix deps.get and mix compile are working fine. I can see Gleam logs during the compilation and the artifacts under _build. Now I’m struggling to find how to import anything from the Gleam package into Elixir. I couldn’t find any module or atom referencing it.

lostbean

lostbean

I tried to add gleam_stdlib in the elixir deps list, mix compile works fine but now when I run iex -S mix I get:

** (Mix) Could not start application gleam_stdlib: could not find application file: gleam_stdlib.app

Not sure if this was expected. I was trying to import stdlib and run a basic test.

Papipo

Papipo OP

Yes, that’s expected because gleam_stdlib does not have an .app file, so you need to add app: false to the dependency in mix.exs. In fact this is true for any hex dependency as well.

lostbean

lostbean

It makes sense. And it is all working now. Thank you so much @Papipo!

One observation is that adding app: false leads to a conflict:

Dependencies have diverged:
* gleam_stdlib (Hex package)
  the dependency gleam_stdlib in apps/buzz_agent/mix.exs is overriding a child dependency:

  > In apps/buzz_agent/mix.exs:
    {:gleam_stdlib, "~> 0.34 or ~> 1.0", [env: :prod, hex: "gleam_stdlib", app: false, repo: "hexpm"]}

  > In /code/claude/corev2/gleam.toml:
    {:gleam_stdlib, ">= 0.34.0 and < 2.0.0", [env: :prod, hex: "gleam_stdlib", repo: "hexpm"]}

  Ensure they match or specify one of the above in your deps and set "override: true"
** (Mix) Can't continue due to errors on dependencies

Adding override: true did fix it (though felt a bit weird having to override it). Also realized I could have used it as a transitive dependency from the gleam package which would have avoided the conflict but led to having direct code usage on transitive packages.

lostbean

lostbean

Another improvement, though possibly unrelated to this, is making the gleam dependency atoms (.e.g. :gleam@list or :gleam@json) visible or searchable in iex. It seems there is some lazy loading because they don’t show up for tab completion in iex, but after you use them once, then they show up.

Papipo

Papipo OP

Yeah, I am aware of the need for override, already looking to fix it.

What you say about iex autocompletion is interesting but I don’t know to do it, I’ll investigate.

Thanks for the feedback!

Papipo

Papipo OP

Can you pull the latest changes on the elixir branch, recompile and try again?

app: false was being forced and I’ve just removed it. This fixed the issue for me.

lostbean

lostbean

After switching to the latest commit, mix compile is failing with:

Unchecked dependencies for environment dev:
* gleam_javascript (Hex package)
  could not find an app file at "_build/dev/lib/gleam_javascript/ebin/gleam_javascript.app". This may happen if the dependency was not yet compiled or the dependency indeed has no app file (then you can pass app: false as option)
* gleam_crypto (Hex package)
  could not find an app file at "_build/dev/lib/gleam_crypto/ebin/gleam_crypto.app". This may happen if the dependency was not yet compiled or the dependency indeed has no app file (then you can pass app: false as option)
* gleam_regexp (Hex package)
  could not find an app file at "_build/dev/lib/gleam_regexp/ebin/gleam_regexp.app". This may happen if the dependency was not yet compiled or the dependency indeed has no app file (then you can pass app: false as option)
* gleam_yielder (Hex package)
  could not find an app file at "_build/dev/lib/gleam_yielder/ebin/gleam_yielder.app". This may happen if the dependency was not yet compiled or the dependency indeed has no app file (then you can pass app: false as option)
* ranger (Hex package)
  could not find an app file at "_build/dev/lib/ranger/ebin/ranger.app". This may happen if the dependency was not yet compiled or the dependency indeed has no app file (then you can pass app: false as option)
* birl (Hex package)
  could not find an app file at "_build/dev/lib/birl/ebin/birl.app". This may happen if the dependency was not yet compiled or the dependency indeed has no app file (then you can pass app: false as option)
* gleeunit (Hex package)
  could not find an app file at "_build/dev/lib/gleeunit/ebin/gleeunit.app". This may happen if the dependency was not yet compiled or the dependency indeed has no app file (then you can pass app: false as option)
* gleam_json (Hex package)
  could not find an app file at "_build/dev/lib/gleam_json/ebin/gleam_json.app". This may happen if the dependency was not yet compiled or the dependency indeed has no app file (then you can pass app: false as option)
* json_blueprint (Hex package)
  could not find an app file at "_build/dev/lib/json_blueprint/ebin/json_blueprint.app". This may happen if the dependency was not yet compiled or the dependency indeed has no app file (then you can pass app: false as option)
** (Mix) Can't continue due to errors on dependencies

with the following gleam deps:

      {:gleam_stdlib, "~> 0.34 or ~> 1.0", app: false, override: true},
      {:gleeunit, "~> 1.0", only: [:dev, :test], runtime: false},
      {:corev2, path: "../../../corev2", app: false}

Only got it “working” by removing the local dep and adding app: false to gleeunit:

      {:gleam_stdlib, "~> 0.34 or ~> 1.0", app: false, override: true},
      {:gleeunit, "~> 1.0", only: [:dev, :test], app: false, runtime: false},
      # {:corev2, path: "../../../corev2", app: false}

Where Next?

Trending in Questions Top

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
jonnycharles
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
spammy
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
silverdr
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated! To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead. Sta...
New
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
bottlenecked
Hi all, I wanted to ask how the community is dealing with post-release steps. Today we have Ecto migrations, which make sure that the db...
New
michallepicki
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the syst...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
type1fool
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
akoutmos
@hugobarauna and I (Alex Koutmos) have been hard at work on writing a book on Nerves that takes you from simply blinking LEDs to building...
New

We're in Beta

About us Mission Statement