typespec-http-zod 0.7.0 → 0.9.0

package/dist/src/api.js

@@ -1046,7 +1046,26 @@ function renderSchemas(registry, externals, routeDeclarations, runtimeModule) {
         const annotation = d.annotated === true ? `: z.ZodType<${d.typeName}>` : "";
         return `\n${declared}\nexport const ${d.identifier}${annotation} = ${d.source};\n`;
     });
-    const parts = [GENERATED_BANNER, '\nimport { z } from "zod";\n'];
+    /**
+     * **Written only when something in the file names it**, like the `ResponseArm` import below and for
+     * the same reason: an unused import fails the lint a generated file has to pass like any other.
+     *
+     * `z` is reached through a declaration's source or a route arm's schema, and a service whose every
+     * operation takes nothing and returns `void` has neither: its arms are
+     * `{ status: 204, schema: undefined }`, which names nothing.
+     * `TS6133: 'z' is declared but its value is never read`, from a compile that reported success. Two
+     * bare `GET`s is where a health check starts, so it is where a new consumer starts.
+     *
+     * **Counting declarations is not sufficient and was the first attempt.** A void-only service HAS
+     * route declarations; they simply do not use Zod. The content decides, and it is TOKENISED on the
+     * language's own identifier rule rather than searched for a substring, so `z` cannot be found
+     * inside `zValidator` or missed beside a bracket. `renderExternalImports` below reads the same
+     * rendered content for the same reason.
+     */
+    const usesZod = new Set([...declarations, ...routeDeclarations].join("").match(/[A-Za-z_$][\w$]*/g) ?? []).has("z");
+    const parts = [GENERATED_BANNER];
+    if (usesZod)
+        parts.push('\nimport { z } from "zod";\n');
     /**
      * A TYPE import, so nothing of this package's survives into the emitted JavaScript.
      *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "typespec-http-zod",
-  "version": "0.7.0",
+  "version": "0.9.0",
   "description": "TypeSpec emitter and library: turn an HTTP service definition into Zod validators and framework-free contract types that agree, keyword for keyword, with the OpenAPI document @typespec/openapi3 publishes from the same source.",
   "keywords": [
     "codegen",