Install

Blog

RSS

Latest · Release

Opal v0.4.1

opal add over day-old metadata drops from 3.0s to 0.56s on a Next.js app, opal --revision names the commit a build came from, and seven framework starters are installed, built, and served by Opal every night.

Sharif

Every post so far is a release · Read them as a book

7 posts

2026

  1. Opal v0.4.0 Release

    Downloads 16 packages at a time, adds opal add and opal remove, and shows what an install is doing while it does it. The Linux binaries run on glibc 2.34 again.

    Sharif

  2. Opal v0.3.1 Release

    Reworks what an install prints, adds opal upgrade to replace the binary in place, and says plainly when opal.lock is missing. The install path itself is unchanged from v0.3.0.

    Sharif

  3. Opal v0.3.0 Release

    Opal now installs the versions npm would: on a Next.js scaffold, 432 of npm's 433 package versions match. Linking runs in parallel, about 2.7× faster than v0.2.1, and an install names every package whose install scripts it didn't run.

    Sharif

  4. Opal v0.2.1 Release

    A performance fix for one finding: a 367-package Next.js install spent most of its time parsing package metadata it never used. Version bodies are now parsed on demand, which took an offline install from 128.6s to 37.7s.

    Sharif

  5. Opal v0.2.0 Release

    Correctness, speed, and visibility across the package manager. Four bugs fixed here produced a wrong node_modules without ever failing an install. opal.lock is now v3.

    Sharif

  6. Opal v0.1.0 Release

    The first release: opal install, with prebuilt binaries for Linux and macOS and an install script.

    Sharif