Dependencies and reuse

Manage Livt Dependencies

Declare package intent, lock the resolved graph, and synchronize local package state without editing downloaded content.

Prerequisite: select the consumer project in the Livt Project view.

Understand the three states

  • livt.toml declares which packages the project requests.
  • livt.lock records the concrete resolved graph.
  • .livt/deps materializes that graph locally and must not be edited.

Add and synchronize a package

  1. Choose Add Dependency from the project or Dependencies node.
  2. Select the package and reviewed version.
  3. Choose Update Lock File.
  4. Choose Sync Dependencies.
  5. Validate the project and run affected tests.
toml 
[dependencies]
"Livt.IO" = "<selected-version>"

Use a local project during coordinated development

toml 
[dependencies]
"Device.Protocol" = { path = "../device-protocol" }

Use project-relative paths so a shared workspace remains portable. Before publishing, replace private local paths with registry selections that consumers can resolve.

Interpret dependency diagnostics

An unsynchronized but valid dependency is recoverable project state and is shown as a warning. A malformed declaration, unavailable package selection, or invalid local project is an error. Synchronization removes the warning when local state agrees with the manifest and lock file.

Warning settings declared by a dependency apply to that dependency's source. Use -W all only when deliberately auditing warnings across the complete graph.

To publish your own reusable project, continue with Packages and Reuse.