Local Packages

A library and its consumer can live side by side on disk and be wired together with a path dependency. arxpm install handles the packaging/install workflow so the Arx compiler finds the library's modules at build time.

Published Arx packages use the same runtime shape: wheels and source distributions include .arxproject.toml plus *.x / *.arx source files. After uv installs registry, Git, or local wheel dependencies, arxpm install leaves source discovery to the installed Arx compiler, which reads package metadata from the active Python environment.

Supported layout

workspace/
├── local_lib/
│   ├── .arxproject.toml
│   └── src/
│       └── local_lib/
│           ├── __init__.x
│           └── stats.x
└── local-consumer/
    ├── .arxproject.toml
    └── src/
        └── local_consumer/
            ├── __init__.x
            └── main.x

Library manifest:

[project]
name = "local_lib"
version = "0.1.0"
requires-arx = ">=1.0"

[build-system]
dependencies = [
  "arxlang>=1.0",
]

[build]
mode = "lib"

Consumer manifest:

[project]
name = "local-consumer"
version = "0.1.0"
requires-arx = ">=1.0"

dependencies = [
  "local_lib @ ../local_lib",
]

[build-system]
dependencies = [
  "arxlang>=1.0",
]

[build]
package = "local_consumer"
mode = "app"

The dependency name on the left of @ must match the library's resolved Arx package name. arxpm install rejects mismatches instead of guessing.

What arxpm install does

For each project.dependencies entry of the form <name> @ <path> where <path> points at a directory containing .arxproject.toml, arxpm install:

1. Validates the library layout.
2. Packs the library to produce a wheel that bundles its .x / .arx sources.
3. Installs the wheel into the consumer's Python environment with uv.
4. Builds and runs through that environment's arx executable, allowing the compiler to resolve the installed package directly.

For registry, Git, or wheel dependencies, arxpm install first lets uv install the requested packages and their metadata-declared transitive dependencies. Normal Python-only dependencies are left untouched, while installed Arx packages become visible to the compiler through their package metadata.

For packaging, arxpm pack and arxpm publish render dependencies into the generated pyproject.toml. Registry dependencies remain plain package names, Git dependencies are rendered as name @ git+..., and path dependencies are rendered by name so published packages can resolve them from the target package index.