Gleam: Keeping dependencies explicit

[NewsBot]

A new Gleam blog post/announcement has been posted!

Gleam is a type safe and scalable language for the Erlang virtual machine and JavaScript runtimes. Today Gleam v0.31.0 has been released, let’s take a look at what’s new.

Requiring explicit dependencies

A Gleam application’s dependency graph contains no duplicate packages, each package has exactly one version.

  ┌───────────────┐
  │               │
  │  Application  │
  │               │
  └───────┬───────┘
          │
   ┌──────▼──────┐
   │             │
   │  library_a  │
   │             │
   └──────┬──────┘
          │
   ┌──────▼──────┐
   │             │
   │  library_b  │
   │             │
   └─────────────┘

Here the application has specified library_a as a dependency in its gleam.toml, and library_a has specified library_b as a dependency in its own gleam...

Get the full details here: Keeping dependencies explicit – Gleam