Skip to content

fix: Emscripten config retains staging paths after catalog installation #246

Description

@zackees

Real WASM validation during kernal-api migration found the installed 4.0.21 package cannot pass its static health check: LLVM_ROOT and BINARYEN_ROOT in .emscripten still name the removed staging directory. install_spec writes config and optionally health-checks before renaming staging to its final package path, but does not relocate that config. Existing archive config tests only write directly to final paths and miss the lifecycle. Fix installation publication and existing managed installs without changing compiler version or JSPI defaults; add a staging-to-final regression and rerun real compiler health plus Blink compile. Refs #242 and zackees/kernal-api#205.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions