fuigo 1.0.2 → 1.0.4

package/bin/fuigo-bootstrap.js

@@ -31,10 +31,25 @@ function readLocalVersion() {
     try { return require('../package.json').version; } catch { return undefined; }
 }
 
+// The platform packages are scoped under the `fuigo` npm org: @fuigo/<platform>-<arch>.
+// The meta package stays unscoped -- it is the name users install, and this is
+// the same split @next, @anthropic-ai and @vscode use for native sidecars.
+//
+// Scoping is not cosmetic. npm's spam filter refuses to CREATE an unscoped
+// package name containing the token `win32-arm64` (403 "Package name triggered
+// spam detection"), which is why fuigo-win32-arm64 never existed at any version
+// and Windows ARM shipped without a binary until 1.0.3. Measured: the refused
+// name fails even when published ALONE ten minutes after a successful sibling,
+// while the same binary under a different name publishes fine. A scope removes
+// that entire class of failure for every platform, not just the one that hit it.
+//
+// The DIRECTORY is still fuigo-<platform>-<arch>; only the npm name is scoped.
+const platformPackageName = (k) => `@fuigo/${k}`;
+
 // Returns null when npm skipped the matching optional dependency
 // (unsupported platform, or --no-optional).
 function resolvePlatformPackageDir() {
-    const platformPkg = `fuigo-${process.platform}-${process.arch}`;
+    const platformPkg = platformPackageName(`${process.platform}-${process.arch}`);
     try {
         return path.dirname(require.resolve(`${platformPkg}/package.json`));
     } catch {
@@ -108,7 +123,7 @@ function resolveBinary() {
     const platformDir = resolvePlatformPackageDir();
     if (!platformDir) {
         console.error(`${pkgName}: no platform binary installed for ${process.platform}-${process.arch}.`);
-        console.error(`  Expected sibling package fuigo-${process.platform}-${process.arch}.`);
+        console.error(`  Expected sibling package ${platformPackageName(`${process.platform}-${process.arch}`)}.`);
         console.error(`  This usually means npm skipped optionalDependencies (e.g. --no-optional)`);
         console.error(`  or the platform is not supported.`);
         process.exit(1);

package/bin/postinstall.js

@@ -40,12 +40,27 @@ if (!SUPPORTED.has(key)) {
     process.exit(0);
 }
 
+// The platform packages are scoped under the `fuigo` npm org: @fuigo/<platform>-<arch>.
+// The meta package stays unscoped -- it is the name users install, and this is
+// the same split @next, @anthropic-ai and @vscode use for native sidecars.
+//
+// Scoping is not cosmetic. npm's spam filter refuses to CREATE an unscoped
+// package name containing the token `win32-arm64` (403 "Package name triggered
+// spam detection"), which is why fuigo-win32-arm64 never existed at any version
+// and Windows ARM shipped without a binary until 1.0.3. Measured: the refused
+// name fails even when published ALONE ten minutes after a successful sibling,
+// while the same binary under a different name publishes fine. A scope removes
+// that entire class of failure for every platform, not just the one that hit it.
+//
+// The DIRECTORY is still fuigo-<platform>-<arch>; only the npm name is scoped.
+const platformPackageName = (k) => `@fuigo/${k}`;
+
 // Resolve the per-platform sibling package's directory. The matching
 // optionalDependency is installed by npm based on `os`/`cpu` filters; the
 // other five are silently skipped. If the matching one is missing, npm was
 // likely invoked with --no-optional or the platform is unsupported.
 function resolvePlatformPackageDir() {
-    const platformPkg = `fuigo-${key}`;
+    const platformPkg = platformPackageName(key);
     try {
         return path.dirname(require.resolve(`${platformPkg}/package.json`));
     } catch {
@@ -180,7 +195,7 @@ function cleanupOldVersions(binName) {
 
 const platformDir = resolvePlatformPackageDir();
 if (!platformDir) {
-    console.error(`fuigo: platform package fuigo-${key} not installed.`);
+    console.error(`fuigo: platform package ${platformPackageName(key)} not installed.`);
     console.error('  This usually means npm was invoked with --no-optional, or the install failed.');
     console.error('  Try: npm install -g fuigo');
     process.exit(0);

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "fuigo",
-    "version": "1.0.2",
+    "version": "1.0.4",
     "description": "Bring Fuigo into your terminal",
     "license": "Apache-2.0",
     "bin": {
@@ -35,11 +35,11 @@
         "@iarna/toml": "^3.0.0"
     },
     "optionalDependencies": {
-        "fuigo-darwin-arm64": "1.0.2",
-        "fuigo-darwin-x64": "1.0.2",
-        "fuigo-linux-arm64": "1.0.2",
-        "fuigo-linux-x64": "1.0.2",
-        "fuigo-win32-arm64": "1.0.2",
-        "fuigo-win32-x64": "1.0.2"
+        "@fuigo/darwin-arm64": "1.0.4",
+        "@fuigo/darwin-x64": "1.0.4",
+        "@fuigo/linux-arm64": "1.0.4",
+        "@fuigo/linux-x64": "1.0.4",
+        "@fuigo/win32-arm64": "1.0.4",
+        "@fuigo/win32-x64": "1.0.4"
     }
 }