Packages

Nytrix packages are source packages. The package manager records direct

dependencies, installs source into an import root, and writes a lockfile with

installed state.

The resolver imports package names the same way it imports modules. The package

manager only decides where source lives and which version or local path was

installed.

Commands

Project layout

myapp/
  ny.pkg.json
  src/main.ny
  .gitignore

After dependency installation:

myapp/
  ny.pkg.json
  ny.pkg.json.lock
  ny_modules/

Imports use package names:

use package_name

Manifest

ny.pkg.json stores metadata and direct dependencies.

{
  "schema": "ny.pkg.v1",
  "name": "myapp",
  "version": "0.1",
  "description": "small tool",
  "author": "Name <mail@example>",
  "license": "MIT",
  "repository": "https://example.com/myapp.git",
  "dependencies": {
    "foo": {"source": "./deps/foo"},
    "bar": {"source": "git+https://example.com/bar.git", "ref": "main"}
  }
}

Sources

#ref or --ref pins a git ref.

Registry

Registry entries map names to sources:

foo = ./deps/foo
bar = git+https://example.com/bar.git#main
repo core = git+https://github.com/owner/ny-packages.git

Registry lookup checks local registry files, configured registry environment,

and the user registry.

The shared Nytrix config files can also hold package repository entries:

~/.config/nytrix/config
./.nytrix/config

Use the same line form:

repo core = git+https://github.com/owner/ny-packages.git
NYTRIX_PKG_HOME=~/.local/share/nytrix/pkg
NYTRIX_PKG_PATH=./ny_modules:./vendor/ny_modules

Environment variables override config defaults. Repository lines are read by

ny pkg repo list, ny pkg search, and ny get.

Package repositories

A package repository root contains package directories:

packages/
  bigint/mod.ny
  crypto_extra/mod.ny

Repository commands:

ny pkg repo add local ./packages
ny pkg repo add core git+https://github.com/owner/ny-packages.git
ny pkg repo list
ny pkg repo sync
ny pkg repo path local
ny pkg repo remove local
ny get bigint
ny pkg search [--interactive] query

repo list prints the configured repository name, source URL/path, and local

cache path. Repository sources can be local paths, git+https://..., SSH Git

URLs, or archives. Config-file repository entries are listed with registry

entries.

ny get <name> checks direct registry entries first, then registered

repositories for <name>/mod.ny or <name>.ny.

ny pkg search <query> scans the same registry and repository sources used by

ny get. Results include package name, source, repository, version, and

description when a package manifest is present.

Use --interactive for the built-in fuzzy picker. The picker is implemented

inside ny; it does not shell out to external fzf.

Install roots

Resolver order includes local modules, vendored modules, venv modules,

configured package path, user package home, and system package home.

Lockfile

ny.pkg.json.lock records installed paths, git refs, source metadata, and

package state. It records installed direct state; it is not a full dependency

solver.

Commit the lockfile for applications when reproducibility matters. Libraries

can keep the manifest broad and document the tested dependency refs in release

notes or examples.

Common package failures

See tooling.md for package command families and

troubleshooting.md for import failures.