@bobfrankston/npmglobalize 1.0.225 → 1.0.227

package/README.md

@@ -486,9 +486,9 @@ not what you meant to publish, so npmglobalize lists the conflicted files and st
 -install, -i    Install globally after publish (from registry)
 -link           Install globally via symlink (npm install -g .)
 -local-install  Install from the local directory only — skip transform/publish, just
-                npm install -g . with file: deps as-is (also -localinstall; -local is
-                the deprecated old spelling). Persisted; a .commitmsg is still logged
-                to npmchanges.md as "(local)"
+                npm install -g . with file: deps as-is (also -localinstall, -install-local,
+                -installlocal; the old -local is an error). Persisted; a .commitmsg is
+                still logged to npmchanges.md as "(local)"
 -global         Clear a persisted -local-install in .globalize.json5 — back to the normal
                 transform/publish flow (publishes to npm again)
 -wsl            Also install in WSL
@@ -898,9 +898,11 @@ This is useful for:
 - Testing a CLI before publishing
 - Projects with `file:` deps that should stay as-is
 
-`-localinstall` is accepted as well. The old spelling `-local` still works but prints a
-deprecation note; it was renamed (2026-09-07) because "local" read as "local mode" rather
-than "install from the local directory".
+`-localinstall`, `-install-local` and `-installlocal` are accepted as well. The old
+spelling `-local` is an error that names the replacement and exits without doing anything;
+it was renamed (2026-09-07) because "local" read as "local mode" rather than "install from
+the local directory", and a warning that then ran the whole cascade anyway was easy to miss
+(2026-09-08).
 
 `-local-install` is persisted to `.globalize.json5` (`"localInstall": true`; the older
 `"local"` key is still read and is rewritten to the new name the next time the file is

package/cli.js

@@ -71,9 +71,9 @@ Install Options:
   -install, -i   Global install after publish (from registry)
   -link          Global install via symlink (npm install -g .)
   -local-install Install from the local directory only — skip transform/publish, just
-                 npm install -g . with file: deps as-is (also -localinstall; -local is
-                 the deprecated old spelling). Persisted; a .commitmsg is still logged
-                 to npmchanges.md as "(local)"
+                 npm install -g . with file: deps as-is (also -localinstall, -install-local,
+                 -installlocal; the old -local is an error). Persisted; a .commitmsg is
+                 still logged to npmchanges.md as "(local)"
   -global        Clear a persisted -local-install in .globalize.json5 — back to the normal
                  transform/publish flow (publishes to npm again)
   -wsl           Also install globally in WSL
@@ -233,15 +233,21 @@ function parseArgs(args) {
             // 2026-09-07 — Claude Code (Fable 5.1), at Bob's direction: "-local is
             // confusing" — it read like "local mode" / "local deps" rather than "install
             // from the local directory". Renamed to -local-install (-localinstall also
-            // accepted). -local still works but says so, so muscle memory isn't broken
-            // and the old spelling is phased out rather than silently kept alive.
-            // The .globalize.json5 key was renamed "local" → "localInstall" the same day;
-            // readConfig accepts the old name and the next persist rewrites it.
+            // accepted). The .globalize.json5 key was renamed "local" → "localInstall"
+            // the same day; readConfig accepts the old name and rewrites it.
+            // 2026-09-08 — Claude Code (Fable 5.1), at Bob's direction: -local is now a
+            // hard error, not a warning. As a warning it printed one yellow line and then
+            // ran the whole cascade anyway (Bob: "you continue rather than exiting"), so
+            // the note scrolled off before it could be acted on. Same exit path as an
+            // unrecognized flag. -install-local / -installlocal are accepted too: the word
+            // order is easy to get backwards (Bob typed "-installlocal" reporting this).
             case '-local':
-                console.log(colors.yellow('!  -local is deprecated — use -local-install (or -localinstall). Same meaning: npm install -g . from the local directory, no publish.'));
-            // falls through
+                options.error = '-local was renamed -local-install (or -localinstall). Same meaning: npm install -g . from the local directory, no publish.';
+                break;
             case '-local-install':
             case '-localinstall':
+            case '-install-local':
+            case '-installlocal':
                 options.localInstall = true;
                 options.explicitKeys.add('localInstall');
                 break;

package/lib.d.ts

@@ -204,7 +204,8 @@ export declare function getUserConfigDir(): string;
 export declare function readUserNpmConfig(): UserNpmConfig;
 /** Write global npm config to %USERPROFILE%\.userconfig\npm.json5 */
 export declare function writeUserNpmConfig(config: UserNpmConfig): void;
-/** Read .globalize.json5 config file */
+/** Read .globalize.json5 config file. A file carrying a renamed key is
+ *  rewritten on the spot, once. */
 export declare function readConfig(dir: string): Partial<GlobalizeOptions>;
 /** Write .globalize.json5 config file */
 export declare function writeConfig(dir: string, config: Partial<GlobalizeOptions>, explicitKeys?: Set<string>): void;

package/lib.js

@@ -304,32 +304,50 @@ export function writeUserNpmConfig(config) {
     const merged = { ...existing, ...config };
     writeUserConfig(merged);
 }
-/** Read .globalize.json5 config file */
-export function readConfig(dir) {
+/** Parse .globalize.json5 and apply key migrations in memory. Does not touch
+ *  the file; readConfig does the rewrite so writeConfig can call this without
+ *  recursing into itself. */
+function parseConfig(dir) {
     const configPath = path.join(dir, '.globalize.json5');
     if (!fs.existsSync(configPath)) {
-        return {};
+        return { config: {}, migrated: false };
     }
     try {
         const content = fs.readFileSync(configPath, 'utf-8');
         const config = JSON5.parse(content);
         // 2026-09-07 — Claude Code (Fable 5.1), at Bob's direction: the "local" key
         // was renamed "localInstall" along with the -local → -local-install flag.
-        // Old files keep working: the value is carried over here, and since
-        // writeConfig reads the existing config through this same function, the
-        // next persist writes the new name and drops the old one.
-        if ('local' in config && !('localInstall' in config)) {
-            config.localInstall = config.local;
-            console.log(colors.dim(`  (.globalize.json5: "local" is now "localInstall" — rewritten on the next persist)`));
+        let migrated = false;
+        if ('local' in config) {
+            if (!('localInstall' in config))
+                config.localInstall = config.local;
+            delete config.local;
+            migrated = true;
         }
-        delete config.local;
-        return config;
+        return { config, migrated };
     }
     catch (error) {
         console.warn(`Warning: Could not parse .globalize.json5 config: ${error.message}`);
-        return {};
+        return { config: {}, migrated: false };
     }
 }
+/** Read .globalize.json5 config file. A file carrying a renamed key is
+ *  rewritten on the spot, once. */
+export function readConfig(dir) {
+    const { config, migrated } = parseConfig(dir);
+    // 2026-09-08 — Claude Code (Fable 5.1), at Bob's direction. The migration
+    // used to be applied in memory only and announced "rewritten on the next
+    // persist" -- on every one of the several readConfig calls a package gets
+    // during a cascade, so the same line printed twice per dep and the file
+    // stayed stale until that package itself published. Now the file is
+    // rewritten immediately; the split into parseConfig keeps writeConfig's
+    // own read from re-entering this rewrite.
+    if (migrated) {
+        writeConfig(dir, config, new Set(['localInstall']));
+        console.log(colors.dim(`  (${path.join(dir, '.globalize.json5')}: renamed "local" to "localInstall")`));
+    }
+    return config;
+}
 /** Inline comments for boolean settings in .globalize.json5. Value-aware: a
  *  negated setting must not read as though it still does the thing (a
  *  `"quiet": false` line saying "Suppress npm warnings" describes the
@@ -374,8 +392,9 @@ export function writeConfig(dir, config, explicitKeys) {
         freeze: false,
         usePaths: true
     };
-    // Read existing config to preserve values
-    const existing = readConfig(dir);
+    // Read existing config to preserve values (parseConfig, not readConfig:
+    // readConfig may rewrite the file, which calls back into writeConfig)
+    const existing = parseConfig(dir).config;
     // Filter out temporary flags and default values (unless explicitly set)
     const filtered = {};
     // upstream is bookkeeping written by recordUpstream, never a CLI option, so

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bobfrankston/npmglobalize",
-  "version": "1.0.225",
+  "version": "1.0.227",
   "description": "Transform file: dependencies to npm versions for publishing",
   "main": "index.js",
   "type": "module",
@@ -34,7 +34,7 @@
     "@bobfrankston/freezepak": "^0.1.9",
     "@bobfrankston/importgen": "^0.1.43",
     "@bobfrankston/themecolors": "^0.1.10",
-    "@bobfrankston/userconfig": "^1.0.12",
+    "@bobfrankston/userconfig": "^1.0.13",
     "@npmcli/package-json": "^7.0.4",
     "json5": "^2.2.3",
     "libnpmversion": "^8.0.3",
@@ -62,7 +62,7 @@
       "@bobfrankston/freezepak": "^0.1.9",
       "@bobfrankston/importgen": "^0.1.43",
       "@bobfrankston/themecolors": "^0.1.10",
-      "@bobfrankston/userconfig": "^1.0.12",
+      "@bobfrankston/userconfig": "^1.0.13",
       "@npmcli/package-json": "^7.0.4",
       "json5": "^2.2.3",
       "libnpmversion": "^8.0.3",