create-eigen-game 0.13.0 → 0.14.0

package/{dist/engine-range.d.ts → src/engine-range.ts}

@@ -7,8 +7,10 @@
  * is not tested. `src/index.ts` uses it; the package `exports` map does not
  * expose it, so it is internal despite being importable by the tests.
  */
+
 /** The dependency whose version the scaffolder emits into the generated server. */
-export declare const ENGINE_PACKAGE = "@eigeninteractive/server";
+export const ENGINE_PACKAGE = "@eigeninteractive/server";
+
 /**
  * The engine range for a scaffolded project, from this package's own
  * `@eigeninteractive/server` devDependency.
@@ -36,4 +38,23 @@ export declare const ENGINE_PACKAGE = "@eigeninteractive/server";
  * @param declared the raw `@eigeninteractive/server` devDependency value
  * @param readSiblingVersion consulted only for the `workspace:` protocol
  */
-export declare function engineRange(declared: string | undefined, readSiblingVersion: () => string | undefined): string;
+export function engineRange(declared: string | undefined, readSiblingVersion: () => string | undefined): string {
+  if (!declared) {
+    throw new Error(`create-eigen-game has no ${ENGINE_PACKAGE} devDependency, which is where the engine range it emits comes from`);
+  }
+
+  const version = declared.startsWith("workspace:") ? readSiblingVersion() : declared;
+
+  if (!version) {
+    throw new Error(`create-eigen-game declares ${ENGINE_PACKAGE} as "${declared}" but the workspace package could not be read, so there is no engine version to emit`);
+  }
+
+  // pnpm packs `workspace:*` as a bare version, which is what makes the caret
+  // below correct. Asserting it means a change in that behaviour fails here
+  // rather than emitting something like `^^0.3.0` into a real project.
+  if (!/^\d+\.\d+\.\d+(?:-[0-9A-Za-z.-]+)?$/.test(version)) {
+    throw new Error(`expected an exact ${ENGINE_PACKAGE} version to build a range from, got "${version}"`);
+  }
+
+  return `^${version}`;
+}