Validate

Before publishing, validate your manifests with nem author lint:

nem author lint pkgs            # lint every package in a catalog
nem author lint pkgs/jq         # lint a single package

By default, linting runs offline: structural checks and syntax validation are performed without fetching or installing any packages. This is the fastest way to catch common mistakes.

Validate the installation

Add --install to attempt installation — every package that passes the offline checks is then fetched, installed, and tested against an isolated NEM_HOME, so a clean result means the package really installs:

nem author lint --install pkgs

Packages are probed in parallel, each against its own isolated NEM_HOME; --jobs N bounds the concurrency (--jobs 1 runs sequentially). When a package fails, its complete install and test output is printed after the run.

A package’s dependsOn entries are resolved from sibling packages in the same catalog, so you can gate a package whose dependencies aren’t published yet. When a chain depends on local packages, lint them bottom-up so each is proven before what builds on it.

Fix any reported findings before publishing. The offline checks also run as the first stage of publishing.