Skip to main content

Module target

Module target 

Source
Expand description

What the target manages its development tools with.

Four managers are recognized by their files: a flake, a mise configuration in the precedence mise documents, asdf’s .tool-versions, and devbox.json. The observation reads the files and reports where the dependency’s name already appears; it judges nothing else.

Structs§

Already
Where a manager file already names the dependency.
ManagerFile
One manager and the file that declares it.
Target
Everything the offline pass reads from the target.

Constants§

MISE_FILES
The mise configuration paths, in mise’s precedence order, the highest first: a file, or a conf.d directory whose *.toml entries all load. A local override file is left out: it is not committed.

Functions§

first_mention
The first line naming name as a word, 1-based.
manager_files
The manager files present, one per manager, in the closed order.
observe
Read the target, offline.
tech_or_node
The technology, with node read from package.json after the version files the bindings define.