codex-token-tracker-nodejs16 0.2.1

package/CHANGELOG.md

@@ -0,0 +1,38 @@
+# Changelog
+
+All notable changes to `codex-token-tracker-nodejs16`.
+
+This package is the Node 16 build of [`codex-token-tracker`](https://www.npmjs.com/package/codex-token-tracker)
+and carries **the same version number**, because it is built from the same sources. For what changed in the
+application itself, see [that package's changelog](https://github.com/CharryLee0426/codex_team_token_tracker/blob/main/packages/menubar/CHANGELOG.md).
+Entries here cover only what is specific to the Node 16 build.
+
+## 0.2.1 — 2026-09-02
+
+First release. Feature-identical to `codex-token-tracker` 0.2.1, installable on Node 16.8+.
+
+### Added
+
+- **Runs on Node 16.8 or newer** — and unchanged on Node 18 / 20 / 22, so a team can standardise on this
+  package if some machines are pinned to an old runtime.
+- **`dist/node16-polyfill.js`**, prepended to every Node-side bundle so it runs before any application or
+  vendored code evaluates. It installs `fetch`/`Headers`/`Request`/`Response`/`FormData`/`File` from
+  [undici](https://github.com/nodejs/undici) (the implementation Node 18 adopted as its built-in fetch),
+  `Blob` from `node:buffer`, the stream classes from `node:stream/web`, WebCrypto `crypto` from
+  `node:crypto`, and `structuredClone` via `node:v8`. Each is installed only when absent, so the polyfill is
+  a no-op on newer Node and inside Electron.
+- **`codex-token-tracker-node16`** as a third command name, for machines where the shared
+  `codex-token-tracker` / `codex-tracker` names would be ambiguous.
+- **`test:node16`**, which runs the upstream suites against this package's own bundle on a real Node 16
+  binary (`node:test` is mapped onto a shim, since Node 16 has no test runner).
+
+### Notes
+
+- No application source of its own: the build bundles `../menubar/src`, so this package cannot drift from
+  the Node 20 one. `scripts/sync-version.mjs` keeps the version aligned on every build.
+- The renderer is built for Chromium 108 (Electron 22) rather than Chromium 128, so the popover still
+  renders if an older Electron has to be used on an older OS.
+- Hermes SQLite session sources are skipped, as they require `node:sqlite`. Not a regression — that module
+  landed in Node 22.5, so the Node 20 build skips them as well.
+- `codex-tracker update` checks and installs `codex-token-tracker-nodejs16`. Its update cache is stored
+  separately from the Node 20 build's, so the two never report each other's published version.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Codex Token Tracker contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,111 @@
+# codex-token-tracker-nodejs16
+
+The **Node.js 16 build** of [`codex-token-tracker`](https://www.npmjs.com/package/codex-token-tracker) — the
+menu bar / system tray app and headless agent that tracks OpenAI Codex token usage, cache hits, model mix
+and API-equivalent cost, and syncs it to your team dashboard.
+
+Same app, same features, same version number. The only difference is the runtime it can be installed on:
+
+| | `codex-token-tracker` | `codex-token-tracker-nodejs16` |
+|---|---|---|
+| Node | 20 or newer | **16.8 or newer** (also runs on 18 / 20 / 22) |
+| Features | all | all |
+| Dashboard / wire protocol | identical | identical |
+
+**Use the regular package unless your machine is pinned to Node 16.** This one exists for build boxes and
+older dev machines whose OS cannot go past Node 16.
+
+## Install
+
+```bash
+npm install -g codex-token-tracker-nodejs16
+codex-tracker            # menu bar app, or headless agent where there is no display
+```
+
+It installs the same `codex-token-tracker` and `codex-tracker` commands as the regular package, plus
+`codex-token-tracker-node16` if you need to disambiguate. Because the command names overlap, install **one
+of the two packages per machine**, not both.
+
+Everything else — commands, configuration, sources, sync, rate limits, what gets uploaded — is documented in
+the [main README](https://github.com/CharryLee0426/codex_team_token_tracker/tree/main/packages/menubar#readme).
+
+## Why a separate package
+
+Node 16 reached end of life in September 2023 and never shipped a global `fetch`. Rather than hold the main
+package back, the Node 16 support lives here:
+
+- **One source tree.** This package contains no application code. Its build bundles `../menubar/src` — the
+  exact same sources the Node 20 package ships — so the two cannot drift apart in features.
+- **`target: node16`.** esbuild downlevels any syntax Node 16 cannot parse.
+- **A polyfill prelude.** `dist/node16-polyfill.js` is prepended to every Node-side bundle and installs the
+  web globals Node 16 lacks, sourced from [undici](https://github.com/nodejs/undici) — which is the very
+  implementation Node 18 adopted as its built-in `fetch`:
+
+  | Global | Source | Missing before |
+  |---|---|---|
+  | `fetch`, `Headers`, `Request`, `Response`, `FormData`, `File` | `undici` | Node 18 |
+  | `Blob` | `node:buffer` | Node 18 |
+  | `ReadableStream`, `WritableStream`, `TransformStream` | `node:stream/web` | Node 18 |
+  | `crypto` (WebCrypto) | `node:crypto` | Node 19 |
+  | `structuredClone` | `node:v8` | Node 17 |
+
+  Every one is installed **only if absent**, so the same bundle is unchanged on newer Node and inside
+  Electron — where the polyfill is a no-op.
+
+## Requirements and caveats
+
+- **Node >= 16.8.** 16.8 is the first release undici's `fetch` supports; 16.20.2 is the last 16.x. Running an
+  older Node prints a clear message instead of a syntax error.
+- **Electron is optional.** It is only needed for the menu bar UI, it brings its own modern Node, and it
+  installs fine under Node 16 (`electron` itself requires only Node >= 12.20). Without a usable Electron or a
+  display, the app automatically runs headless — `codex-tracker agent` — which does all the tracking and
+  uploading. If your OS is too old for Electron 38, install an older one alongside it
+  (`npm i -g electron@22`); the renderer is built for Chromium 108 so it still works.
+- **Hermes SQLite sources are skipped**, because they need `node:sqlite`. This is not a regression: that
+  module only arrived in Node 22.5, so the Node 20 build skips them too.
+- **Self-update stays on this package.** `codex-tracker update` checks and installs
+  `codex-token-tracker-nodejs16`, never the Node 20 package.
+
+## Development
+
+Built from the monorepo; it needs `../menubar/src` present.
+
+```bash
+pnpm --filter codex-token-tracker-nodejs16 build          # dev build
+pnpm --filter codex-token-tracker-nodejs16 build:release   # what prepack/publish runs
+pnpm --filter codex-token-tracker-nodejs16 typecheck
+pnpm --filter codex-token-tracker-nodejs16 test            # suites on the current Node
+pnpm --filter codex-token-tracker-nodejs16 test:node16      # suites on a real Node 16
+```
+
+`test:node16` finds the newest Node 16 under `~/.nvm/versions/node`, or uses `NODE16_BIN`. It runs the
+upstream suites against the node16 bundle, with `node:test` mapped onto a small shim since Node 16 has no
+test runner.
+
+### End-to-end
+
+```bash
+pnpm e2e:node16            # from the repo root
+pnpm e2e:node16:gui        # also downloads Electron (~100 MB) and launches the tray app
+```
+
+This does what a user does: builds a release, packs a tarball, installs it with **Node 16's own npm**
+under `--engine-strict`, and drives the installed binary on a real Node 16 — 35 checks across the
+polyfill, the CLI surface, the self-updater and a headless agent cycle.
+
+The load-bearing assertion is **differential**: the same synthetic Codex fixtures are fed to both the
+Node 16 build (on Node 16) and the Node 20 build (on your Node), and the two `status --json` reports must
+be byte-identical once timestamps are masked. A port that silently drops a source, mis-parses a number or
+takes a different branch cannot pass that.
+
+The run is hermetic — `CODEX_TRACKER_HOME` sends config, state and the update cache to a temp dir (so the
+run is signed out and **nothing can upload**), `CODEX_HOME` and friends point the scanner at fixtures
+rather than your real sessions, and local stub servers stand in for the npm registry and the dashboard, so
+it needs no network. It restores your dev builds and deletes its scratch directory on the way out; pass
+`--keep` to inspect it.
+
+The version is kept identical to `codex-token-tracker` by `scripts/sync-version.mjs`, which every build runs.
+
+## License
+
+MIT © Chen Li

package/bin/codex-tracker.js

@@ -0,0 +1,18 @@
+#!/usr/bin/env node
+"use strict";
+// Kept to ES5 syntax on purpose: this file has to parse on whatever ancient Node the user typed the
+// command with, so that a too-old runtime produces the message below instead of a SyntaxError.
+var v = process.versions.node.split(".");
+var major = parseInt(v[0], 10);
+var minor = parseInt(v[1], 10);
+if (major < 16 || (major === 16 && minor < 8)) {
+  console.error(
+    "codex-token-tracker-nodejs16 requires Node >= 16.8 (this is Node " +
+      process.versions.node +
+      ").\nNode 16.8 is the first release its bundled fetch implementation supports; 16.20.2 is the last 16.x."
+  );
+  process.exit(1);
+}
+// dist/cli.js begins by requiring dist/node16-polyfill.js (injected as an esbuild banner), which
+// installs fetch and the other web globals Node 16 lacks before any application code runs.
+require("../dist/cli.js");