fixing documentation

scripts/linked-deps.mjs

@@ -26,7 +26,7 @@ if (!target) {
 const read = (dir) => JSON.parse(fs.readFileSync(path.join(dir, 'package.json'), 'utf-8'));
 
 // Resolved by name rather than by directory: nothing guarantees that
-// `@bitsquare/nopy-cube` lives in `packages/nopy-cube`.
+// `@bitsquare/nopy-cubes` lives in `packages/nopy-cubes`.
 const versionByName = new Map(
   fs
     .readdirSync(PACKAGES_DIR)

scripts/publish-order.mjs

@@ -3,7 +3,7 @@
 /**
  * Prints the publishable workspace package directories, dependencies first.
  *
- * `packages/*` in alphabetical order puts `nopy` ahead of the `nopy-cube` it
+ * `packages/*` in alphabetical order puts `nopy` ahead of the `nopy-cubes` it
  * depends on, which leaves a window where the registry holds a package whose
  * dependency does not exist yet. Ordering the publish by the workspace graph
  * closes it. One directory per line, so the caller can `for dir in $(…)`.

scripts/try-snapshot.mjs

@@ -5,7 +5,7 @@
  * project, and runs it.
  *
  * This is the rehearsal that the local `pnpm pack` check cannot be: it goes to
- * the real registry, resolves the real `@bitsquare/nopy-cube` version that
+ * the real registry, resolves the real `@bitsquare/nopy-cubes` version that
  * `pnpm publish` baked into the tarball, and puts a real `nopy` binary on disk.
  * A tarball that installs here is one a user can install.
  *
@@ -26,7 +26,7 @@ import path from 'node:path';
 const SCOPE = '@bitsquare';
 const DEFAULT_REGISTRY = 'https://gitea.bitsquare.dev/api/packages/BitSquare/npm/';
 const CLI_PACKAGE = '@bitsquare/nopy';
-const BUNDLE_PACKAGE = '@bitsquare/cubes-core';
+const BUNDLE_PACKAGE = '@bitsquare/nopy-cubes-core';
 
 const args = process.argv.slice(2);
 
@@ -101,17 +101,17 @@ try {
 
   // The whole point of packing with pnpm: this must be a concrete version, not
   // the literal string `workspace:*`.
-  const linked = installed.dependencies?.['@bitsquare/nopy-cube'];
+  const linked = installed.dependencies?.['@bitsquare/nopy-cubes'];
   if (!linked || linked.startsWith('workspace:')) {
     throw new Error(
-      `${CLI_PACKAGE} declares nopy-cube as "${linked}" — a workspace range escaped.`
+      `${CLI_PACKAGE} declares nopy-cubes as "${linked}" — a workspace range escaped.`
     );
   }
 
   console.log('\n--- versions ---');
   console.log(`${CLI_PACKAGE}@${installed.version}`);
   console.log(`${BUNDLE_PACKAGE}@${bundle.version}`);
-  console.log(`  -> @bitsquare/nopy-cube ${linked}`);
+  console.log(`  -> @bitsquare/nopy-cubes ${linked}`);
 
   console.log('\n--- nopy --version ---');
   console.log(capture(path.join(dir, 'node_modules', '.bin', 'nopy'), ['--version']));
@@ -139,7 +139,7 @@ try {
       [
         ...discovery
           .replace(ansi, '')
-          .matchAll(/([a-z0-9:_-]+) - [^\n]*\(@bitsquare\/cubes-core\)/g),
+          .matchAll(/([a-z0-9:_-]+) - [^\n]*\(@bitsquare\/nopy-cubes-core\)/g),
       ].map((match) => match[1])
     ),
   ];

scripts/verify-pack.mjs

@@ -3,7 +3,7 @@
 /**
  * Asserts that every publishable package is installable once packed.
  *
- * `@bitsquare/nopy` depends on `@bitsquare/nopy-cube` through `workspace:*`, and
+ * `@bitsquare/nopy` depends on `@bitsquare/nopy-cubes` through `workspace:*`, and
  * `link-workspace-packages` is off, so a plain semver range would resolve from
  * the registry instead of linking the workspace copy — the protocol is not
  * optional. But npm has no idea what `workspace:` means: a tarball that still