@bobfrankston/npmglobalize 1.0.212 → 1.0.213

package/README.md

@@ -421,8 +421,8 @@ not what you meant to publish, so npmglobalize lists the conflicted files and st
 -link           Install globally via symlink (npm install -g .)
 -local          Local install only — skip transform/publish, just npm install -g .
                 (persisted; a .commitmsg is still logged to npmchanges.md as "(local)")
--nolocal        Clear a persisted -local in .globalize.json5 — back to transform/publish
-                (alias: -global)
+-global         Clear a persisted -local in .globalize.json5 — back to the normal
+                transform/publish flow (publishes to npm again)
 -wsl            Also install in WSL
 -once           Don't persist flags to .globalize.json5
 ```
@@ -773,7 +773,7 @@ npmglobalize -local      # same as --local
 Some flags are **persisted** to `.globalize.json5` when set from the CLI:
 - `-install`, `-link`, `-wsl`, `-files`, `-fix` — install/build preferences
 - `-np` (noPublish) — once set, prevents accidental publishes
-- `-local` — remembers "this project is local-only" (clear with `-nolocal` / `-global`)
+- `-local` — remembers "this project is local-only" (clear with `-global`)
 - `-git`/`-npm` visibility
 
 Other flags are **one-shot** (never persisted):
@@ -793,7 +793,7 @@ Skip all transform/publish logic and just run `npm install -g .` with `file:` de
 ```bash
 npmglobalize -local          # Install globally from local directory
 npmglobalize -local -wsl     # Also install in WSL
-npmglobalize -nolocal        # Back to the normal transform/publish flow (alias: -global)
+npmglobalize -global         # Back to the normal transform/publish flow (publishes to npm)
 ```
 
 This is useful for:
@@ -802,7 +802,7 @@ This is useful for:
 - Projects with `file:` deps that should stay as-is
 
 `-local` is persisted to `.globalize.json5` (`"local": true`), so a bare
-`npmglobalize` keeps doing local installs until you run `-nolocal` (or edit the
+`npmglobalize` keeps doing local installs until you run `-global` (or edit the
 file). Nothing is committed, bumped, or published, but a `.commitmsg` is still
 consumed: it is appended to `npmchanges.md` under a
 `## v<version> (local) — <YYYY-MM-DD>` header and deleted, so the notes are not

package/cli.js

@@ -70,8 +70,8 @@ Install Options:
   -link          Global install via symlink (npm install -g .)
   -local         Local install only — skip transform/publish, just npm install -g .
                  (persisted; a .commitmsg is still logged to npmchanges.md as "(local)")
-  -nolocal       Clear a persisted -local in .globalize.json5 — back to transform/publish
-                 (alias: -global)
+  -global        Clear a persisted -local in .globalize.json5 — back to the normal
+                 transform/publish flow (publishes to npm again)
   -wsl           Also install globally in WSL
   -freeze        Freeze node_modules (replace symlinks with real copies for network shares)
   -nofreeze      Disable freeze
@@ -157,7 +157,7 @@ Examples:
   npmglobalize -link -wsl            Release + link on Windows and WSL (symlink)
   npmglobalize -local                Install locally with file: deps as-is (no publish)
   npmglobalize -local -wsl           Local install on Windows and WSL
-  npmglobalize -nolocal              Leave local-only mode; publish normally from now on
+  npmglobalize -global               Leave local-only mode; publish to npm from now on
   npmglobalize -np                   Just transform, no publish (remembered in config)
   npmglobalize -cleanup              Restore original dependencies
   npmglobalize -init                 Initialize git (adopt existing remote if any) + release
@@ -233,7 +233,8 @@ function parseArgs(args) {
             // 2026-09-01 16:30 EDT — Claude Code (Opus 5), at Bob's direction. -local
             // persists to .globalize.json5 but had no counterpart, so leaving local-only
             // mode meant hand-editing the config. Same shape as -publish for -np.
-            case '-nolocal':
+            // 2026-09-01 15:00 EDT — Bob: "-global makes more sense, -nolocal is confusing";
+            // -nolocal dropped, -global is the only spelling.
             case '-global':
                 options.local = false;
                 options.explicitKeys.add('local');

package/lib.js

@@ -445,7 +445,7 @@ export function writeConfig(dir, config, explicitKeys) {
         ['"gitVisibility": "private"', 'Git repo: private or public'],
         ['"npmVisibility": "private"', 'npm package: private or public'],
         ['"fix": false', 'true = auto-run npm audit fix'],
-        ['"local": false', 'true = local install only (skip transform/publish); clear with -nolocal'],
+        ['"local": false', 'true = local install only (skip transform/publish); clear with -global'],
         ['"noPublish": false', 'true = transform but don\'t publish'],
         ['"freeze": false', 'true = freeze node_modules (replace symlinks with real copies)'],
         ['"usePaths": true', 'true = resolve file: deps from siblings; false = use latest npm version (standalone)'],
@@ -6053,7 +6053,7 @@ async function doLocalInstall(cwd, options) {
     const pkgVersion = pkg.version || '0.0.0';
     console.log(colors.blue(`Local install: ${pkgName}@${pkgVersion}`));
     console.log(colors.dim('Skipping transform/publish — installing with file: deps as-is'));
-    console.log(colors.dim('  (switch back to the publish flow with -nolocal)'));
+    console.log(colors.dim('  (switch back to the publish flow with -global)'));
     // Record before the bin check: a library's notes are history too.
     recordLocalChange(cwd, pkgVersion, dryRun);
     if (!pkg.bin) {

package/package.json

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