@bobfrankston/npmglobalize 1.0.210 → 1.0.212

package/README.md

@@ -257,6 +257,7 @@ Notes:
 - **Git/GitHub only.** npm publish does not consume git commit messages; `npmchanges.md` lives in the git repo and on GitHub but is excluded from the published npm tarball (the standard `*.md` rule keeps only `README.md`).
 - If both `-m` and `.commitmsg` are present, `-m` wins and `.commitmsg` is left alone (not consumed).
 - If publish fails, `.commitmsg` is preserved for the next attempt.
+- Under `-local` (no publish) the file is still consumed — appended as `## v<version> (local) — <date>` and deleted, with no git commit. See [Local Install](#local-install--local).
 - `.commitmsg` is auto-added to `.npmignore` (security pattern) so it never leaks into the tarball.
 
 ### 🔧 Git Integration & Error Recovery
@@ -419,6 +420,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          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)
 -wsl            Also install in WSL
 -once           Don't persist flags to .globalize.json5
 ```
@@ -769,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"
+- `-local` — remembers "this project is local-only" (clear with `-nolocal` / `-global`)
 - `-git`/`-npm` visibility
 
 Other flags are **one-shot** (never persisted):
@@ -789,6 +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)
 ```
 
 This is useful for:
@@ -796,6 +801,14 @@ This is useful for:
 - Testing a CLI before publishing
 - 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
+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
+lost. Several local entries may share one version number — the date tells them
+apart. No git commit is made for it; the next real publish carries it along.
+
 ### Private Packages
 
 Packages with `"private": true` in `package.json` skip the npm publish step. Dependencies are still transformed and restored — the publish is the only thing skipped.

package/cli.js

@@ -69,6 +69,9 @@ Install Options:
   -install, -i   Global install after publish (from registry)
   -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)
   -wsl           Also install globally in WSL
   -freeze        Freeze node_modules (replace symlinks with real copies for network shares)
   -nofreeze      Disable freeze
@@ -154,6 +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 -np                   Just transform, no publish (remembered in config)
   npmglobalize -cleanup              Restore original dependencies
   npmglobalize -init                 Initialize git (adopt existing remote if any) + release
@@ -226,6 +230,14 @@ function parseArgs(args) {
                 options.local = true;
                 options.explicitKeys.add('local');
                 break;
+            // 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':
+            case '-global':
+                options.local = false;
+                options.explicitKeys.add('local');
+                break;
             case '-install':
             case '-i':
                 options.install = true;

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)'],
+        ['"local": false', 'true = local install only (skip transform/publish); clear with -nolocal'],
         ['"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)'],
@@ -6000,7 +6000,52 @@ export function getToolVersion() {
         return 'unknown';
     }
 }
-/** Perform local-only install (npm install -g .) — extracted for reuse from git-init prompts */
+// 2026-09-01 16:30 EDT — Claude Code (Opus 5), at Bob's direction.
+// Under -local the run returned before any of the .commitmsg handling, so the
+// notes a local-only package accumulated in .commitmsg were never recorded
+// anywhere — they sat in the file, and the next edit overwrote them. A local
+// install is still a change worth a history line, so the same npmchanges.md
+// gets the entry, tagged "(local)" because nothing was published or bumped
+// (several local runs may legitimately share one version number). No git
+// activity: -local is the path taken when there is often no repo at all, and
+// when there is one the next real publish commits npmchanges.md with the rest.
+/** Consume .commitmsg for a -local run: append to npmchanges.md, delete the file. */
+function recordLocalChange(cwd, version, dryRun) {
+    const commitMsgPath = path.join(cwd, '.commitmsg');
+    if (!fs.existsSync(commitMsgPath))
+        return;
+    let content;
+    try {
+        content = fs.readFileSync(commitMsgPath, 'utf-8').trim();
+    }
+    catch (err) {
+        console.error(colors.yellow(`  Warning: could not read .commitmsg: ${err.message}`));
+        return;
+    }
+    if (!content)
+        return;
+    if (dryRun) {
+        console.log(`  [dry-run] Would append .commitmsg to npmchanges.md as v${version} (local) and delete it`);
+        return;
+    }
+    try {
+        const npmChangesPath = path.join(cwd, 'npmchanges.md');
+        const date = new Date().toISOString().slice(0, 10);
+        const entry = `## v${version} (local) — ${date}\n\n${content}\n\n`;
+        const existing = fs.existsSync(npmChangesPath)
+            ? fs.readFileSync(npmChangesPath, 'utf-8')
+            : '# npm Publish Changes\n\n';
+        const sep = existing.endsWith('\n') ? '' : '\n';
+        fs.writeFileSync(npmChangesPath, existing + sep + entry);
+        fs.unlinkSync(commitMsgPath);
+        console.log(colors.green(`  ✓ Appended .commitmsg to npmchanges.md as v${version} (local) and removed .commitmsg`));
+    }
+    catch (err) {
+        console.error(colors.yellow(`  Warning: could not update npmchanges.md: ${err.message}`));
+    }
+}
+/** Perform local-only install (npm install -g .) — the single -local path, reached
+ *  from the -local flag / config and from the git-init prompts' "local only" choice. */
 async function doLocalInstall(cwd, options) {
     const { dryRun = false, wsl = false } = options;
     const pkg = readPackageJson(cwd);
@@ -6008,6 +6053,9 @@ 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)'));
+    // Record before the bin check: a library's notes are history too.
+    recordLocalChange(cwd, pkgVersion, dryRun);
     if (!pkg.bin) {
         console.log(colors.dim(`  (library — skipping global install)`));
         return true;
@@ -6018,8 +6066,15 @@ async function doLocalInstall(cwd, options) {
             console.log('  [dry-run] Would run: wsl npm install -g .');
         return true;
     }
-    // 2026-09-01 10:55 EDT — Claude Code: see the note on the sibling local-install
-    // path — captured, distilled output instead of raw npm chatter.
+    // 2026-09-01 10:55 EDT — Claude Code (Opus 5), at Bob's direction. Was a
+    // raw streamed `npm install -g .`, so the terminal got npm's chatter
+    // verbatim — including `npm warn allow-scripts .npmrc allow-scripts
+    // setting is being ignored because --allow-scripts was passed`, a
+    // warning npmglobalize provokes on itself by passing that flag, and
+    // which no reader can act on. installGlobalWithRetry captures the
+    // output and prints only what matters (the added/changed/removed line,
+    // or distilled errors plus a log file), which is what every other
+    // install path here already does.
     const result = await installGlobalWithRetry('.', cwd, false, 1);
     if (result.success) {
         console.log(colors.green(`✓ Installed locally: ${pkgName}@${pkgVersion}`));
@@ -6120,51 +6175,11 @@ export async function globalize(cwd, options = {}, configOptions = {}) {
     // -local is testing-only and must NOT mutate package.json — packages are meant to be installed
     // as published public packages by end users; the bin field is whatever the published shape is.
     // Library members (no bin) are silently skipped: nothing for global install to expose.
+    // 2026-09-01 16:30 EDT — Claude Code (Opus 5): this was a verbatim copy of
+    // doLocalInstall (the 10:55 output-capture note lives there now). One path,
+    // so the .commitmsg recording added today lands in both entry points.
     if (local) {
-        const pkg = readPackageJson(cwd);
-        const pkgName = pkg.name || path.basename(cwd);
-        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'));
-        if (!pkg.bin) {
-            console.log(colors.dim(`  (library — skipping global install)`));
-            return true;
-        }
-        if (dryRun) {
-            console.log('  [dry-run] Would run: npm install -g .');
-            if (wsl)
-                console.log('  [dry-run] Would run: wsl npm install -g .');
-            return true;
-        }
-        // 2026-09-01 10:55 EDT — Claude Code (Opus 5), at Bob's direction. Was a
-        // raw streamed `npm install -g .`, so the terminal got npm's chatter
-        // verbatim — including `npm warn allow-scripts .npmrc allow-scripts
-        // setting is being ignored because --allow-scripts was passed`, a
-        // warning npmglobalize provokes on itself by passing that flag, and
-        // which no reader can act on. installGlobalWithRetry captures the
-        // output and prints only what matters (the added/changed/removed line,
-        // or distilled errors plus a log file), which is what every other
-        // install path here already does.
-        const result = await installGlobalWithRetry('.', cwd, false, 1);
-        if (result.success) {
-            console.log(colors.green(`✓ Installed locally: ${pkgName}@${pkgVersion}`));
-        }
-        else {
-            console.error(colors.red(`✗ Local install failed`));
-            console.error(colors.yellow('  Try running manually: npm install -g .'));
-            return false;
-        }
-        if (wsl) {
-            console.log(`Installing ${pkgName} in WSL (local)...`);
-            const wslResult = await installInWsl(['npm', 'install', '-g', '.'], { cwd });
-            if (wslResult.success) {
-                console.log(colors.green(`✓ Installed in WSL: ${pkgName}@${pkgVersion}`));
-            }
-            else {
-                console.error(colors.yellow('✗ WSL install failed (is npm installed in WSL?)'));
-            }
-        }
-        return true;
+        return doLocalInstall(cwd, options);
     }
     // Prescan the file: dep graph up front — surface all problems before
     // any transform/publish, so the user can fix them once and run clean.

package/package.json

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