Skip to main content

Module doctor

Module doctor 

Source
Expand description

The prerequisite walkthrough, mechanized — and the knowledge every other verb inlines into its own failures.

One table describes every tool a Frame application depends on: what it is, which command proves it, and where to install it. frame doctor walks the whole table; every other verb asks require for exactly the subset it is about to use, so a missing tool surfaces at the earliest, most fixable moment as a typed refusal carrying its install link — a raw “command not found” never reaches the user.

Structs§

MissingTools
Every tool a verb needs but the machine lacks, with install links — batched so one refusal names every gap instead of dribbling them out.
Tool
One prerequisite tool: its user-facing name, the command that proves it, and the install link a refusal carries.

Constants§

CHROME_INSTALL
Install link a missing-Chrome refusal carries.

Statics§

ALL_TOOLS
The whole walkthrough, in the order the doctor reports it.
BUILD_PREREQUISITES
Tools frame run and frame build refuse without: the host build chain only — a fresh scaffold’s page is already compiled, so Node enters only when page sources change.
CHECK_PREREQUISITES
Tools frame check refuses without.
ERLANG
Erlang/OTP: the VM toolchain Gleam compiles through.
GLEAM
Gleam: compiles and tests the application’s component.
NEW_PREREQUISITES
Tools frame new refuses without: everything the generated application needs to build, verify, and run.
NODE
Node.js: typechecks the page and drives the browser proof.
NPM
npm: installs the page’s type and proof toolchain.
RUST
The Rust toolchain: builds and tests the application’s host.

Functions§

probe
Probes one tool and returns the first line of its version report.
require
Requires every listed tool, batching all gaps into one typed refusal.
require_chrome
Resolves the installed Chrome the browser proof drives: CHROME_BIN when set, the default macOS installation path otherwise.
warn_if_chrome_missing
Warns loudly (without refusing) when Chrome is missing: creating, building, and running an application need no browser, but frame test’s default verdict includes the real-browser proof and will refuse until one is installed.