bea

Community

Bea is young, and the people trying it now shape what it becomes. Conversation happens with the Gleam community, and the code is all in the open on GitHub.

Talk on the Gleam Discord

Bea has a topic on the Gleam Discord: ask questions, share what you've built, or follow the compiler's development. Bea is Gleam underneath, so it belongs with the Gleam community.

Open the Bea topic

Report what breaks

Found code that doesn't compile, a confusing error, or a formatter that refuses your file? Open an issue with the smallest .bea file that shows it. bea transpile file.bea output helps a lot.

Open an issue

Contribute to the compiler

The compiler is written in Bea: lexer, parser, deriving, lowering, code generation, formatter and language server, each in its own module, with tests in Gleam. Build it with bea build, test it with bea test. Pick something from the issues or bring a proposal.

Browse the source

Add to the examples

The first six chapters of the tour are built from beacode/, Bea solutions to the Gleam exercism track. A new solution there becomes a new lesson here.

See beacode

Improve this site

This site is a Bea project too: Lustre views written in Bea, rendered on Node, with the browser parts compiled to JavaScript. Fixes to the tour notes are as welcome as fixes to the code.

Site source

Set up your editor

bea lsp runs Gleam's language server on the generated code and maps every position back to your .bea files: diagnostics, hover, completion, go to definition, rename and formatting. The VS Code extension lives in editors/vscode.

vim.filetype.add({ extension = { bea = "bea" } })
vim.api.nvim_create_autocmd("FileType", {
  pattern = "bea",
  callback = function(args)
    vim.lsp.start({
      name = "bea",
      cmd = { "bea", "lsp" },
      root_dir = vim.fs.root(args.buf, { "bea.toml" }),
    })
  end,
})

Beatrix the black hole is Bea's mascot, and a cousin of Gleam's Lucy. Use her when you write or talk about Bea.