little-coder 1.4.2 → 1.4.3

package/CHANGELOG.md

@@ -2,6 +2,21 @@
 
 All notable changes to little-coder are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and little-coder's public interface (CLI, providers, tools, skills) follows semver starting at `v0.0.1` post-rename.
 
+## [v1.4.3] — 2026-05-19
+
+Follow-up to v1.4.2: clean up two cosmetic regressions that the @earendil-works scope migration surfaced.
+
+### Fixed
+- **Pi's `What's New` block no longer appears inside little-coder's TUI after a version bump.** Root cause: pi's interactive mode reads its own bundled `CHANGELOG.md` on startup and renders every entry strictly newer than the `lastChangelogVersion` field in `~/.pi/agent/settings.json` (`interactive-mode.js:getChangelogForDisplay`). v1.4.2 jumped the bundled pi from 0.68.1 to 0.75.3, so users who had previously launched any older little-coder saw pi's full 0.68 → 0.75 upstream changelog dumped *underneath* little-coder's own startup banner. That's wrong because little-coder is the surface and pi is the substrate — the chrome above shouldn't suddenly start advertising the substrate's release notes. The launcher (`bin/little-coder.mjs`) now pre-stamps `lastChangelogVersion` to the currently bundled pi version (resolved from `node_modules/@earendil-works/pi-coding-agent/package.json#version`, the same file we already read to find pi's cli.js, so there's no second source of truth) *before* pi starts. Pi then sees "user already saw this changelog" and the block never renders. The merge into `~/.pi/agent/settings.json` is non-destructive — `quietStartup: true` and every other existing key are preserved. Users who genuinely want pi's upstream changelog can still pull it up with `/changelog` inside the TUI.
+- **`npm install -g little-coder` no longer prints `node-domexception@1.0.0` deprecation warning.** Root cause: a 5-hop transitive — `@earendil-works/pi-ai` → `@google/genai` → `google-auth-library` → `gaxios` → `node-fetch@3` → `fetch-blob@3` → `node-domexception@1.0.0`. The `node-domexception` package is just a 16-line shim that sets `globalThis.DOMException` when undefined, and native `DOMException` has been built into Node since 18 — so on our `Node >= 22.19` floor, the entire shim is dead code. Replaced it via `package.json#overrides` pointing at a bundled stub at `./vendor/node-domexception/` that exports `module.exports = globalThis.DOMException` directly. The stub ships in the npm tarball (`files` array now includes `vendor/`). Since npm's `overrides` field is honored when little-coder is the install root (which it is for `npm install -g little-coder`), the deprecated upstream package never reaches the user's tree, and npm prints no warning. Functional behavior is identical because the only call site (`fetch-blob/from.js:import DOMException from 'node-domexception'`) sees the same `globalThis.DOMException` it would have gotten from the upstream shim.
+
+### Notes for upgraders
+- The bundled stub lives at `vendor/node-domexception/` inside the published package — it's listed under `files` in `package.json`. If you'd added your own `overrides` field that touches `node-domexception` in a hand-rolled fork of little-coder, our entry will take precedence when you publish; in the unlikely case that breaks something for you, override it back in your fork's root `package.json`.
+- The `lastChangelogVersion` pre-stamp is one-directional: it writes the *currently bundled* pi version into settings on every launch. If you'd like to see pi's upstream changelog for a future bump, `/changelog` inside the TUI is the unconditional path — it doesn't consult `lastChangelogVersion`.
+- No CLI flag, models.json shape, skill-pack, extension API, or per-model profile changes. Little-coder's own startup banner, tagline, and keybind hints (the branding extension at `.pi/extensions/branding/`) are byte-for-byte unchanged from v1.4.2.
+
+---
+
 ## [v1.4.2] — 2026-05-19
 
 Bundled-pi maintenance release. Closes [#22](https://github.com/itayinbarr/little-coder/issues/22), [#23](https://github.com/itayinbarr/little-coder/issues/23), [#25](https://github.com/itayinbarr/little-coder/issues/25). The pi runtime moves from `@mariozechner/pi-coding-agent@^0.68.1` to `@earendil-works/pi-coding-agent@^0.75.3` — same author, same project, new npm scope — which makes the deprecation warnings disappear, pulls in pi's recent Windows / undici / cmd-shim fixes, and (because pi 0.75 raised its floor) bumps the supported Node range to ≥ 22.19. No CLI flag, settings, extension API, or skill-pack changes.

package/bin/little-coder.mjs

@@ -131,15 +131,30 @@ if (process.env.PI_SKIP_VERSION_CHECK === undefined) {
   process.env.PI_SKIP_VERSION_CHECK = "1";
 }
 
-// ---- 8. Force pi's global quietStartup so the loaded-resources block stays hidden ----
-// Pi's interactive mode dumps an [Extensions] / [Skills] / [Prompts] block on
-// every launch unless `quietStartup: true` is set in its global settings
-// (~/.pi/agent/settings.json). Our shipped .pi/settings.json doesn't reach pi
-// because pi reads from <cwd>/.pi/settings.json (project) or <agentDir>/settings.json
-// (global), neither of which is our npm-installed package dir. So the launcher
-// non-destructively merges quietStartup: true into the user's actual global
-// settings file. Existing keys are preserved. To see the full inventory, run
-// `little-coder --verbose` — pi's verbose flag overrides quietStartup.
+// ---- 8. Force pi's global quietStartup + pin lastChangelogVersion ----
+// Two non-destructive merges into ~/.pi/agent/settings.json (or the dir pointed
+// to by PI_CODING_AGENT_DIR):
+//
+//   1. quietStartup: true
+//        Pi's interactive mode otherwise dumps an [Extensions] / [Skills] /
+//        [Prompts] inventory on every launch. Pi reads global settings from
+//        <agentDir>/settings.json — NOT from our npm-installed package dir —
+//        so our shipped .pi/settings.json doesn't reach it. To see the
+//        inventory anyway, run `little-coder --verbose`.
+//
+//   2. lastChangelogVersion: <currently installed pi version>
+//        Pi reads its own bundled CHANGELOG.md on startup and renders a
+//        "What's New" block for every entry strictly newer than this stored
+//        version (interactive-mode.js:getChangelogForDisplay). That makes pi's
+//        upstream changelog show up inside little-coder's TUI every time we
+//        bump the bundled pi dep — which is jarring because little-coder is
+//        the surface, not pi. We pre-stamp this field to the version we just
+//        bundled BEFORE pi starts, so pi sees "user already saw this", and
+//        the block never renders. Users who genuinely want to read pi's
+//        upstream changelog can still do so with `/changelog` inside the TUI.
+//
+// Existing keys are preserved. We only write when the desired value differs
+// from what's already on disk, so this is a no-op on warm launches.
 try {
   const agentDirEnv = process.env.PI_CODING_AGENT_DIR;
   let agentDir;
@@ -164,8 +179,32 @@ try {
       globalSettings = {};
     }
   }
+
+  // Read the bundled pi version. We resolve via the same package.json we used
+  // to find piEntry, so this stays consistent with whichever pi we actually
+  // spawn — no second source of truth.
+  let bundledPiVersion;
+  try {
+    const piPkgJson = JSON.parse(
+      readFileSync(join(piPkgRoot, "package.json"), "utf-8"),
+    );
+    if (typeof piPkgJson?.version === "string") bundledPiVersion = piPkgJson.version;
+  } catch {
+    // If we can't read pi's version, fall back to leaving lastChangelogVersion
+    // alone — pi will then show its own changelog on the next launch. Better
+    // than writing garbage into the user's settings.
+  }
+
+  let mutated = false;
   if (globalSettings.quietStartup !== true) {
     globalSettings.quietStartup = true;
+    mutated = true;
+  }
+  if (bundledPiVersion && globalSettings.lastChangelogVersion !== bundledPiVersion) {
+    globalSettings.lastChangelogVersion = bundledPiVersion;
+    mutated = true;
+  }
+  if (mutated) {
     writeFileSync(globalSettingsPath, JSON.stringify(globalSettings, null, 2));
   }
 } catch {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "little-coder",
-  "version": "1.4.2",
+  "version": "1.4.3",
   "description": "A pi-based coding agent optimized for small local language models. Reproduces the whitepaper's scaffold-model-fit adaptations as pi extensions.",
   "homepage": "https://github.com/itayinbarr/little-coder",
   "repository": {
@@ -23,6 +23,7 @@
     ".pi/extensions/",
     ".pi/settings.json",
     "models.json",
+    "vendor/",
     "LICENSE",
     "NOTICE",
     "README.md",
@@ -39,6 +40,9 @@
     "@sinclair/typebox": "^0.34.49",
     "playwright": "^1.59.1"
   },
+  "overrides": {
+    "node-domexception": "file:./vendor/node-domexception"
+  },
   "devDependencies": {
     "typescript": "^5.6.0",
     "vitest": "^2.1.0"

package/vendor/node-domexception/index.js

@@ -0,0 +1,9 @@
+// Drop-in replacement for the deprecated `node-domexception@1.0.0` shim.
+// Bundled with little-coder; wired in via `package.json#overrides` so the
+// transitive `fetch-blob -> node-domexception` chain (pulled in via
+// @earendil-works/pi-ai -> @google/genai -> google-auth-library -> gaxios ->
+// node-fetch -> fetch-blob) doesn't emit a deprecation warning during
+// `npm install -g little-coder`. Native `globalThis.DOMException` has been
+// available since Node 18, and little-coder requires Node >= 22.19, so this
+// is always defined at import time.
+module.exports = globalThis.DOMException;

package/vendor/node-domexception/package.json

@@ -0,0 +1,10 @@
+{
+  "name": "node-domexception",
+  "version": "1.0.1",
+  "description": "Bundled with little-coder. Returns Node's native globalThis.DOMException (built-in since Node 18). Replaces the deprecated upstream node-domexception@1.0.0 via npm overrides so `npm install -g little-coder` no longer prints its deprecation warning. We pin engines.node to >= 18 because that's where native DOMException landed; the launcher's own preflight enforces >= 22.19, so this is satisfied transitively.",
+  "main": "index.js",
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "license": "MIT"
+}