Skip to main content
Pinega
Use dark themeMenu

Reference

Web build and environment

Exact current command and environment reference for the Pinega Web workspace. For an end-to-end task procedure, use the corresponding how-to pages.

Toolchain

SurfaceCurrent contract
Node.js>=26.0.0; CI pins 26.7.0
Package managernpm with committed package-lock.json
Playwright1.62.1
Browser containermcr.microsoft.com/playwright:v1.62.1-noble when a matching container is required
Build targetES2022 static multi-page output

Package scripts

CommandPurpose
npm run tokens:checkVerify generated Strata token adapters are current.
npm run typecheckStrict TypeScript check without emission.
npm run test:unitDesign and Web architecture/content contracts.
npm run buildGenerate the static site and discovery artefacts.
npm run check:buildValidate generated output and budgets.
npm run serveServe web/dist at the configured local address.
npm run test:browserChromium/Firefox/WebKit browser and accessibility suite.
npm run test:visualChromium desktop visual-regression baselines.

Generated outputs

  • web/dist/ — static site.
  • site-manifest.json — public/content route metadata projection.
  • content/documentation-manifest.json — documentation-only search/readiness projection.
  • sitemap.xml and robots.txt — discovery files derived from registry flags.
  • assets/ — bundled CSS/JavaScript and Web Awesome assets.

Build budgets

The current build check enforces aggregate JavaScript and CSS budgets. Treat the values in web/scripts/check-build.mjs as authoritative because they are executable CI policy, not prose-only targets.