Going to production
The final stretch: lint, test, and a real deploy — the same path this very site followed, published on GitHub Pages.
nexa lint
nexa lint
# [NEXA-SEO-001] missing `title` in `seo`
# Error: `nexa lint` found warningsCompiles every page without writing dist/ and fails if the SEO Analyzer or package warnings found anything — meant to block a merge in CI.
nexa test
nexa test
# Compiling the project before running tests...
# Running `npm test`...Compiles the project (a fresh dist/, with the Fase 23 hashed filenames) and runs the project's JS test runner against that build.
nexa add nginx
nexa add nginx
# Generates deploy/nginx.conf — gzip, security headers,
# a year-long immutable cache only for hashed files.Generates a real deploy/nginx.conf: gzip, security headers, and a year-long immutable cache only for the files that genuinely carry a content hash.
Done
dist/ is 100% static — any host serves it. This complete tutorial ends here: you now have what it takes to take a real Nexa project to production.