Packages for the whole pack.

01 / Project files and NQON

project.nqon is a data manifest, not executable code. Runtime/nqon.mjs and Tools/nqon.mjs parse portable NQON independently of the compiler. It supports bare/quoted strings, objects, arrays, finite numbers, booleans, null and comments; duplicate keys are invalid.

name = demo
version = "0.1.0"
entry = "src/main.noqeri"
packages {
    toolkit = "1.2.0"
}

02 / Start and validate a project

The Stage-0 CLI exposes new, manifest, lock and audit. Run each in the actual repository/project context rather than assuming an npm-compatible package.json workflow.

noqeri new demo
noqeri manifest demo/project.nqon
noqeri lock demo/project.nqon
noqeri audit demo

03 / Resolver and registry boundaries

Runtime/package-manager.mjs implements namespace/name@semver coordinates, checksum verification, offline cache and bounded package traversal. Registry releases live outside the compiler repo and are not guaranteed to exist for every dependency name.

04 / Standard library versus packages

Lib/std contains checked source modules for numeric, collections, JSON, HTTP, cryptography, concurrency, graphics and more. Several capabilities are host/extern interfaces requiring a linked provider; a source module's existence does not guarantee every environment executes it.

05 / The lockfile matters

A lockfile pins dependency/version/integrity selections. Validate provenance before using code, especially packages with native bindings, separately licensed artifacts or unqualified registry endpoints.