streamline package naming

packages/nopy/src/cubes/dependencies.ts

@@ -3,7 +3,7 @@
  * @module cubes/dependencies
  */
 
-import type { Cube, CubeVariables, HookContext } from '@bitsquare/nopy-cube';
+import type { Cube, CubeVariables, HookContext } from '@bitsquare/nopy-cubes';
 import { getLogger } from '@logtape/logtape';
 import type { Variables } from '../nopy.common.js';
 import type { NopyConfig } from '../nopy.config.js';

packages/nopy/src/cubes/index.ts

@@ -17,7 +17,7 @@ export type {
   Hook,
   HookContext,
   LoadResult,
-} from '@bitsquare/nopy-cube';
+} from '@bitsquare/nopy-cubes';
 export {
   Cube,
   createManifest,
@@ -26,7 +26,7 @@ export {
   uniqid,
   zodInner,
   zodKind,
-} from '@bitsquare/nopy-cube';
+} from '@bitsquare/nopy-cubes';
 // Dependencies
 export { BuildContext } from './dependencies.js';
 // Loader

packages/nopy/src/cubes/loader.ts

@@ -5,7 +5,7 @@
 
 import module from 'node:module';
 import path from 'node:path';
-import { Cube, type CubeSource, type LoadResult, type Manifest } from '@bitsquare/nopy-cube';
+import { Cube, type CubeSource, type LoadResult, type Manifest } from '@bitsquare/nopy-cubes';
 import { z } from 'zod';
 import { fs } from 'zx';
 import { loadConfig } from '../nopy.config.js';
@@ -15,7 +15,7 @@ let hookRegistered = false;
 
 /**
  * Installs the fallback resolver that lets a manifest in a bare directory
- * import `@bitsquare/nopy-cube` or `zod` — see `resolve-hook.mjs`.
+ * import `@bitsquare/nopy-cubes` or `zod` — see `resolve-hook.mjs`.
  *
  * `module.register()` is process-global and cannot be undone, so this runs once
  * and only when cubes are about to be imported. Registration failing is not

packages/nopy/src/cubes/resolve-hook.mjs

@@ -5,7 +5,7 @@
  * A manifest is loaded with `import(manifestPath)`, so its imports resolve from
  * its own directory. A cube sitting in an arbitrary `cubeDirs` entry — no
  * package.json above it, no node_modules beside it — therefore cannot import
- * `@bitsquare/nopy-cube` or `zod` at all, and the run dies on
+ * `@bitsquare/nopy-cubes` or `zod` at all, and the run dies on
  * ERR_MODULE_NOT_FOUND before a single deploy is built.
  *
  * A published cube bundle never reaches this: it declares its own dependencies
@@ -25,7 +25,7 @@ import { pathToFileURL } from 'node:url';
  * be expected to install for itself. Anything else stays a hard failure — a
  * cube that wants a library should depend on it.
  */
-const FALLBACK_ROOTS = ['@bitsquare/nopy-cube', '@bitsquare/nopy', 'zod'];
+const FALLBACK_ROOTS = ['@bitsquare/nopy-cubes', '@bitsquare/nopy', 'zod'];
 
 /** @type {NodeRequire | undefined} */
 let fallbackRequire;

packages/nopy/src/nopy.executor.ts

@@ -3,7 +3,7 @@
  * @module nopy.executor
  */
 
-import type { DependencySpec } from '@bitsquare/nopy-cube';
+import type { DependencySpec } from '@bitsquare/nopy-cubes';
 import { getLogger } from '@logtape/logtape';
 import { execa } from 'execa';
 import { MASK } from './nopy.common.js';