Package registry

In the works

Vyi already has local packages: a directory with a package.vyipac manifest, relative imports inside the package root, and @-prefixed standard-library packages resolved from the packages path. What is still coming is the rest of the ecosystem loop:

• A package registry — publish packages by name and version, resolve deps from the manifest, and install them into a local dependency store. Registry metadata such as hasBuiltIns, hasInlineMarkers, hasFileSystemAccess, hasNetworkAccess, and supportedTargets is recorded when a package is published — not set in application manifests.
• Rendered package docs — a program that extracts documentation from package source and publishes it here, so every uploaded package is browsable and searchable on this site.
• A broader standard library — more packages beyond the core set that ships today (@core, @io, @mem, and friends), grown alongside the registry.

Until that lands, third-party dependencies can be declared in the manifest, but fetch-and-install tooling is not available yet. Local packages and the shipped standard library work now.

What you can do today

• Structure a project as a package with package.vyipac — see Modules and packages.
• Use the standard library packages documented under Docs → Standard library.
• Read the manifest schema for name, version, deps, entries, and export.