Standard library

These are the built-in modules for the Erlang target: lists, HTTP, HTML, databases, processes, AI sessions, and more. Click a name for signatures and docs.

JavaScript projects use selm's client platform instead of this BEAM stdlib: Browser, Html, Http, Json.Decode, Random, and related client packages, built into the compiler with nothing to install. On the BEAM, modules are grouped by job: core types, bytes, JSON, database and cache (including column types), auth, HTML and web, AI, processes, config and IO, and testing.

New to form validation? Start with the Forms guide, then open Changeset and Changeset.Validate below.

Core

Bytes

JSON

Validation

Database

Cache

Auth

HTML & web

AI

Processes

Config & IO

Observability

Testing

Other

Not available on the BEAM

Some Elm packages are browser-only: Browser, Html.Events, Http, and Browser.Navigation stay on the JavaScript target. BEAM apps use selm's Random, Url.Builder, Bytes, and File stdlib; the client platform keeps Elm's versions of those modules.

Worked dice example for both sides: examples/10_random (SPA Random.generate as a Cmd, server Random.generate / Random.step).

On the BEAM you still have Platform, Cmd, Sub, Task, Url, and Url.Parser. Outbound HTTP uses Req (Elixir Req-style); inbound servers use Server. File.read / File.write are filesystem tasks (not the browser picker); dual-target pin: fixtures/file_dual. Time.every delivers Posix; named zones use Time.getZone (not the client Time.here / Time.utc API). Dual-target pin: fixtures/time_dual. BEAM Process is Subject / call / listen (not client Id / spawn / kill); dual-target pin: fixtures/process_dual. JSON responses usually go through Server.json.