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 export and raiku import are complementary commands for capturing and restoring your Raiku package environment using a human-readable plain-text file. export writes one line per installed package (name, version, language, and optionally the SHA-256 hash) to requirements.raiku. import reads that file and installs every package it contains. Together they are the easiest way to share a Raiku environment between teammates, bootstrap CI, or onboard a new developer without requiring them to know which packages to install.

Usage

# Export
raiku export [--output FILE] [--language LANG]

# Import
raiku import [--file FILE] [--trust] [--no-build]

Flags

raiku export

FlagShortDefaultDescription
--output-orequirements.raikuFile to write the package list to.
--language-lallExport only packages for one language.

raiku import

FlagShortDefaultDescription
--file-frequirements.raikuRequirements file to read.
--trustfalseSkip build-command confirmation for all packages during import.
--no-buildfalseDownload and cache packages only; skip all build commands.

requirements.raiku format

The file is plain text — one package per line, comments starting with # are ignored:
# Raiku requirements file
# Generated by: raiku export
# Install with: raiku import

blazing-vec==1.0.0  # Rust  --hash sha256:a3c8f1d2e4b7...
fast-math==1.2.0    # Python  --hash sha256:9f3e2a1c5d8b...
goqueue==0.9.1      # Go
Each non-comment line follows the format: <name>==<version>. The # <Language> comment and --hash annotation are written by raiku export but are not required for raiku import to work — the importer looks up version and language from the index at install time.

Use cases

ScenarioCommands
Share environment with a teammateraiku export → commit requirements.raiku → teammate runs raiku import
CI environment bootstrapraiku import --file requirements.raiku --no-build
Developer onboardingClone repo, run raiku import — done
Language-specific snapshotraiku export --language Rust --output rust-deps.raiku

Examples

raiku export
raiku import installs packages using their names and versions from the requirements file, going through the standard install flow including hash verification. It does not guarantee byte-for-byte identical installs across machines in the way that raiku from-lock does. For fully reproducible installs with locked hashes, use raiku from-lock with a committed raiku.lock.
Commit requirements.raiku to your repository so new contributors can get up and running with a single command:
raiku import
For CI, add raiku import --no-build to your setup step.

Build docs developers (and LLMs) love