DEVELOPER PREVIEWPACKAGES ARE LOCKED BY IMMUTABLE REVISION

Abla, meeting
the real world.

These packages were built alongside the compiler to pressure-test the language against web servers, wire protocols, browser code, native Android, and large test suites.

import github("AndreBaltazar8/abla-web")thenablac package update --project .
02
HTML + WASM

Abla MVC

Typed escaped HTML, the $mvcview subparser, typed server actions, and automatic extraction of integer client actions to WebAssembly.

WEBWASM
03
ANDROID

Abla Mobile

Application state, rendering, and event logic in Abla, delivered through a reusable Jetpack Compose host without application Kotlin source.

ANDROIDCOMPOSE
04
DATABASE

Abla Postgres

A PostgreSQL v3 wire client with parameterized queries, reusable authenticated sessions, and SCRAM-SHA-256—without libpq or a sidecar.

POSTGRESQLSCRAM
05
CACHE

Abla Redis

A direct RESP client with reusable authenticated connections, RESP2 and RESP3 values, bounded transport, ACLs, and common operations.

REDISRESP3
06
MESSAGING

Abla NATS

A Core NATS client for publish/subscribe, queues, request/reply, headers, authentication, and bounded protocol reads.

NATSPUB/SUB
07
TOOLING

Abla Test Runner

A bounded parallel runner written in Abla: isolated processes, structured commands, dependencies, timeouts, per-step logs, and exclusive barriers.

TESTINGPARALLEL

Updating is explicit.
Building never moves the lock.

package update resolves provider expressions and writes an immutable revision to abla.lock. Commit that file.

Ordinary builds use the locked graph. --offline prevents a Git cache fill, and package vendor creates an air-gapped source tree.

Read about package imports