Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/SGizek/Raiku/llms.txt

Use this file to discover all available pages before exploring further.

raiku from-lock reads a raiku.lock file and installs every package at the exact version and hash recorded in it. Unlike raiku import (which uses a human-readable requirements file and resolves versions through the index), raiku from-lock bypasses version resolution entirely — you get precisely what was locked, every time, on every machine. This makes it the right tool for CI pipelines, production deployments, and any workflow where reproducibility is non-negotiable.

​
Usage

raiku from-lock [--file FILE] [--trust] [--no-build] [--force]

​
Flags

FlagShortDefaultDescription
--file-fraiku.lockLock file to read. Defaults to raiku.lock in the current directory.
--trustfalseSkip build-command confirmation for all packages.
--no-buildfalseDownload and cache only; skip all build commands.
--forcefalseReinstall packages even if they are already present in the cache at the locked version.

​
Behavior

  1. Reads the lock file specified by --file (default: ./raiku.lock).
  2. For each locked package: checks whether the exact version is already cached.
    • If cached (and --force is not set): skips with a ✓ already installed message.
    • If not cached: installs the exact version recorded in the lock entry.
  3. When the local index is available, Raiku uses index metadata (author, description, path) enriched with the locked version. If the index is unavailable, it falls back to the path and hash stored directly in the lock file.
  4. Reports a summary of installed, skipped, and failed packages.

​
Difference from raiku import

raiku importraiku from-lock
Source filerequirements.raikuraiku.lock
Version resolutionResolved through index at install timeExact version from lock — no resolution
Hash enforcementVia index on installLocked SHA-256 used directly
Human-editableYesNo — generated by raiku install --lock
Reproducibility guaranteeBest-effortExact

​
Creating a lock file

A raiku.lock is written (or updated) whenever you install with --lock: 
raiku install fast-math --lock
raiku install goqueue --lock

​
Examples

raiku from-lock

​
Sample output

Installing 3 package(s) from raiku.lock

  ✓ fast-math v1.0.0 already installed
  → goqueue v0.9.1
  ✓ goqueue v0.9.1 installed
  → blazing-vec v1.0.0
  ✓ blazing-vec v1.0.0 installed

Results: 2 installed  1 already up to date
Commit raiku.lock to source control and use raiku from-lock in your CI pipeline. This guarantees that every build — developer machine, CI runner, or production container — uses identical package versions. Pair with raiku install --lock whenever you add or update a dependency.
If readonly mode is enabled in your configuration, raiku from-lock will exit immediately. Disable it with raiku config set readonly false before running installs.

Build docs developers (and LLMs) love

Get started for freeTalk to us