Danil Silantyev 69c9f2e83c fix(cli): print the real package version for --version ...

printVersion() logged `process.env.npm_package_version ?? '0.2.0'`. npm only
populates npm_package_version inside its own run-script env, so an end user
running `npx pxpipe-proxy --version` or a globally-installed `pxpipe` got the
stale hardcoded fallback (0.2.0) instead of the real version — the code comment
even claimed an esbuild.define that was never wired up.

- scripts/build.mjs reads package.json and inlines the version via esbuild
  `define: { __PXPIPE_VERSION__ }`, then smoke-checks the built binary
  (`node dist/node.js --version` must equal package.json) and fails the build
  on mismatch, so a broken injection can never ship.
- src/node.ts reads the injected constant behind a `typeof` guard (safe under
  tsx, where it is undefined), falling back to npm_package_version then
  'unknown' — never a stale release number.

Verified: node dist/node.js --version now prints 0.8.0.

2026-07-04 18:50:48 -04:00

..

build.mjs

fix(cli): print the real package version for --version

2026-07-04 18:50:48 -04:00

gen-atlas.ts

feat(render): raise page ceiling to ~1932x1932 and align gate/paging geometry

2026-06-17 10:01:33 -04:00

restart.sh

chore: rename all pixelpipe references to pxpipe

2026-06-09 19:04:09 -04:00

vendor-ui.mjs

feat(dashboard): replace Svelte bundle with AHA stack (htmx + Alpine, server-rendered fragments)

2026-06-09 22:17:53 -04:00