@bobfrankston/npmglobalize 1.0.214 → 1.0.215

package/cli.js

@@ -2,7 +2,7 @@
 /**
  * npmglobalize CLI - Transform file: dependencies to npm versions for publishing
  */
-import { globalize, globalizeWorkspace, installCleanupHandlers, readConfig, readPackageJson, readUserNpmConfig, writeConfig, writePackageJson, getBuildIssues, clearBuildIssues, ensureFileDepModules, buildProject, buildFileDepsTopologically, reportTs7Deprecations, fixTs7Deprecations } from './lib.js';
+import { globalize, globalizeWorkspace, installCleanupHandlers, readConfig, readPackageJson, readUserNpmConfig, writeConfig, writePackageJson, getBuildIssues, clearBuildIssues, ensureFileDepModules, buildProject, buildFileDepsTopologically, reportTs7Deprecations, fixTs7Deprecations, canonicalCase } from './lib.js';
 import fs from 'fs';
 import path from 'path';
 import { colors } from './colors.js';
@@ -549,6 +549,19 @@ export async function main() {
             process.exit(1);
         }
     }
+    // 2026-09-06 — Claude Code (Fable 5.1), at Bob's direction.
+    // `process.cwd()` carries whatever letter case the shell was started with
+    // (`y:\dev\...` from a lowercase prompt). Every `file:` junction npm writes
+    // inherits that case, and mixed `y:`/`Y:` junction targets are exactly what
+    // makes arborist crash with "Cannot read properties of null (reading
+    // 'package')" — see `caseDiffers` in lib.ts. Canonicalizing once up front
+    // means every npm the cascade spawns writes junctions with the on-disk
+    // spelling, so the repair in verifyDepPathCase stops being needed again.
+    const canonicalCwd = canonicalCase(cwd);
+    if (canonicalCwd && canonicalCwd !== cwd) {
+        cwd = canonicalCwd;
+        process.chdir(cwd);
+    }
     // Report-only TS7-readiness scan (no transform / build / publish).
     if (cliOptions.ts7Report) {
         printTs7Report(cwd);

package/lib.d.ts

@@ -287,6 +287,16 @@ export type UnpublishedDep = {
     path: string;
     reason: 'new' | 'update';
 };
+/** The canonical on-disk spelling of `target`, or null if it does not exist.
+ *  Windows answers path queries case-insensitively, so the only way to learn how
+ *  a directory is really spelled is to ask its parent to list it — a segment at a
+ *  time, from the root down. The drive letter is always uppercased.
+ *
+ *  2026-09-06 — Claude Code (Fable 5.1), at Bob's direction: exported so cli.ts can
+ *  canonicalize the working directory at startup (see there for why). Deliberately
+ *  NOT `fs.realpathSync.native`: that would also resolve a junction the user is
+ *  standing inside, which is a behaviour change nobody asked for. */
+export declare function canonicalCase(target: string): string;
 /** Vet the casing of every `file:` dependency path, in BOTH places it is recorded:
  *  the spec in package.json and the junction npm created in node_modules.
  *

package/lib.js

@@ -1323,8 +1323,13 @@ function hasLocalChanges(packageName, version, targetPath, verbose) {
 /** The canonical on-disk spelling of `target`, or null if it does not exist.
  *  Windows answers path queries case-insensitively, so the only way to learn how
  *  a directory is really spelled is to ask its parent to list it — a segment at a
- *  time, from the root down. */
-function canonicalCase(target) {
+ *  time, from the root down. The drive letter is always uppercased.
+ *
+ *  2026-09-06 — Claude Code (Fable 5.1), at Bob's direction: exported so cli.ts can
+ *  canonicalize the working directory at startup (see there for why). Deliberately
+ *  NOT `fs.realpathSync.native`: that would also resolve a junction the user is
+ *  standing inside, which is a behaviour change nobody asked for. */
+export function canonicalCase(target) {
     const full = path.resolve(target);
     if (!fs.existsSync(full))
         return null;
@@ -1347,10 +1352,22 @@ function canonicalCase(target) {
     return cur;
 }
 /** True when two paths name the same place but are spelled with different case
- *  in a directory name. A bare drive-letter difference (`y:` vs `Y:`) doesn't
- *  count — it resolves identically everywhere, including WSL's /mnt/y. */
+ *  anywhere — the drive letter included.
+ *
+ *  2026-09-06 — Claude Code (Fable 5.1), at Bob's direction. This used to strip the
+ *  root before comparing, on the theory that `y:` vs `Y:` "resolves identically
+ *  everywhere". It does on the filesystem; it does NOT inside npm's arborist.
+ *  Traced with an instrumented `loadActual` on dbitemx / pings / itemw: arborist
+ *  keeps the junction target's case in `realpath` (an exact-string index) but
+ *  computes `location` with `path.win32.relative`, which folds drive-letter case.
+ *  One directory reached as `Y:\...` and `y:\...` becomes two target nodes at one
+ *  location; the second clobbers the first, every Link into the first is left with
+ *  `target === null`, and the next same-case Link crashes on `target.package` —
+ *  the "Cannot read properties of null (reading 'package')" failure. npm writes
+ *  the junction target with whatever drive case the cwd had, so a lowercase shell
+ *  is all it takes. Full trace: `.llm/arborist-trace.md`. */
 function caseDiffers(a, b) {
-    const strip = (p) => p.replace(/[\\/]+$/, '').slice(path.parse(p).root.length);
+    const strip = (p) => p.replace(/[\\/]+$/, '');
     return strip(a) !== strip(b);
 }
 /** Vet the casing of every `file:` dependency path, in BOTH places it is recorded:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bobfrankston/npmglobalize",
-  "version": "1.0.214",
+  "version": "1.0.215",
   "description": "Transform file: dependencies to npm versions for publishing",
   "main": "index.js",
   "type": "module",