@defold-typescript/types 0.11.3 → 0.11.5

package/index.d.ts

@@ -81,3 +81,8 @@ export {
   type ScriptProperty,
 } from "./src/lifecycle";
 export { type WrapOptions, wrapAsAmbientGlobal } from "./src/publish-dts";
+export {
+  lookupSignature,
+  type SignatureOverride,
+  type SignatureStore,
+} from "./src/signature-store";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@defold-typescript/types",
-  "version": "0.11.3",
+  "version": "0.11.5",
   "description": "TypeScript types for the Defold engine's Lua APIs.",
   "license": "MIT",
   "repository": {

package/scripts/regen.ts

@@ -148,6 +148,10 @@ export interface MessagesManifestEntry {
   readonly outFile: string;
 }
 
+// Unlike MODULE_MANIFEST, this surface is hand-maintained: Defold ships no
+// machine-readable export for built-in message ids, so refresh fixtures/
+// messages_doc.json by hand from the Defold API reference. The
+// message-payload-drift test guards the payload shapes against drift.
 export const MESSAGES_MANIFEST: MessagesManifestEntry = {
   doc: messagesDoc,
   outFile: "builtin-messages.d.ts",

package/scripts/signature-store-fs.ts

@@ -0,0 +1,33 @@
+import { readFileSync } from "node:fs";
+import { resolve } from "node:path";
+import type { SignatureStore } from "../src/signature-store";
+
+// Build-time only: lives under `scripts/` (never reachable from the shipped
+// `src/index.ts` graph) so its `node:fs` import cannot leak into a consumer's
+// typecheck. `src/signature-store.ts` stays pure for exactly that reason.
+export const IO_SIGNATURES_PATH = resolve(import.meta.dir, "..", "signatures", "io.json");
+export const STRING_SIGNATURES_PATH = resolve(import.meta.dir, "..", "signatures", "string.json");
+export const TABLE_SIGNATURES_PATH = resolve(import.meta.dir, "..", "signatures", "table.json");
+export const OS_SIGNATURES_PATH = resolve(import.meta.dir, "..", "signatures", "os.json");
+export const COROUTINE_SIGNATURES_PATH = resolve(
+  import.meta.dir,
+  "..",
+  "signatures",
+  "coroutine.json",
+);
+export const MATH_SIGNATURES_PATH = resolve(import.meta.dir, "..", "signatures", "math.json");
+export const BIT_SIGNATURES_PATH = resolve(import.meta.dir, "..", "signatures", "bit.json");
+export const DEBUG_SIGNATURES_PATH = resolve(import.meta.dir, "..", "signatures", "debug.json");
+export const PACKAGE_SIGNATURES_PATH = resolve(import.meta.dir, "..", "signatures", "package.json");
+export const BASE_SIGNATURES_PATH = resolve(import.meta.dir, "..", "signatures", "base.json");
+export const SOCKET_SIGNATURES_PATH = resolve(import.meta.dir, "..", "signatures", "socket.json");
+
+export function loadSignatureFile(path: string): SignatureStore {
+  let raw: string;
+  try {
+    raw = readFileSync(path, "utf8");
+  } catch {
+    return {};
+  }
+  return JSON.parse(raw) as SignatureStore;
+}

package/src/engine-globals.d.ts

@@ -1,6 +1,10 @@
 /** @noSelfInFile */
 import type * as Core from "./core-types";
 
+// Hand-maintained surface: Defold ships no machine-readable export for the
+// prefixless globals, so add or remove entries here from the Defold API
+// reference and mirror the change in fixtures/globals_doc.json — the
+// engine-globals test fails if the two fall out of sync.
 declare global {
   type Hash = Core.Hash;
   function hash(s: string): Core.Hash;

package/scripts/signature-store-io.ts

@@ -1,18 +0,0 @@
-import { readFileSync } from "node:fs";
-import { resolve } from "node:path";
-import type { SignatureStore } from "../src/signature-store";
-
-// Build-time only: lives under `scripts/` (never reachable from the shipped
-// `src/index.ts` graph) so its `node:fs` import cannot leak into a consumer's
-// typecheck. `src/signature-store.ts` stays pure for exactly that reason.
-const IO_SIGNATURES_PATH = resolve(import.meta.dir, "..", "signatures", "io.json");
-
-export function loadSignatures(path: string = IO_SIGNATURES_PATH): SignatureStore {
-  let raw: string;
-  try {
-    raw = readFileSync(path, "utf8");
-  } catch {
-    return {};
-  }
-  return JSON.parse(raw) as SignatureStore;
-}