@suss/extractor 0.5.8 → 0.5.10

package/dist/index.d.cts

@@ -945,6 +945,19 @@ interface ContractPattern {
     paramsExtraction?: {
         property: string;
     };
+    /**
+     * Where the reader finds one endpoint's contract object. Left out,
+     * the ts-rest shape applies: one contract object contains every
+     * endpoint keyed by handler name, and the reader walks up from the
+     * handler to the enclosing router call. With `registrationArgument`,
+     * the zod-openapi shape applies instead: `app.openapi(route, handler)`
+     * passes the endpoint's own contract as the handler's sibling
+     * argument.
+     */
+    endpoint?: {
+        from: "registrationArgument";
+        position: number;
+    };
 }
 type InputMappingPattern = {
     /** Single object parameter, e.g. React Router LoaderFunctionArgs */
@@ -1234,6 +1247,24 @@ interface PatternPack {
      * available without importing anything).
      */
     requiresImport?: string[];
+    /**
+     * Environment variables the pack's library reads from inside
+     * node_modules, where no walk ever looks. Declaring them keeps the
+     * checker from telling a template that a variable is unused when the
+     * library reads it on every invocation. The adapter emits one marker
+     * summary per entry whose `module` some project file imports, and
+     * the runtime-config pairing consults the markers before it accuses.
+     * The module match is a specifier prefix, so one entry covers a
+     * scoped family like `@aws-lambda-powertools/`.
+     */
+    libraryEnvVars?: Array<{
+        /** Module-specifier prefix the library's imports start with. */
+        module: string;
+        /** Env-var name prefixes the library reads, e.g. "POWERTOOLS_". */
+        prefixes?: string[];
+        /** Exact env-var names the library reads. */
+        names?: string[];
+    }>;
     /**
      * Library wrappers that return the function they wrapped. The adapter
      * works this out on its own for a factory inside the project by reading
@@ -1245,6 +1276,40 @@ interface PatternPack {
      * `"Sentry.wrapHandler"`.
      */
     transparentWrappers?: TransparentWrapper[];
+    /**
+     * How this library's client object is constructed, so an operation
+     * summary can say which endpoint its calls go to. Each entry is a
+     * constructor or factory imported from `importModule`, with
+     * `uriProperty` the option key whose value is the endpoint. The
+     * adapter reads every construction in the project and stamps the
+     * client on each operation summary when exactly one distinct client
+     * exists; two or more distinct clients abstain, since a hook call
+     * does not say which one it goes through.
+     */
+    graphqlClients?: Array<{
+        importModule: string;
+        importName: string;
+        uriProperty: string;
+    }>;
+    /**
+     * Which service a client talks to, keyed by the endpoint the
+     * construction was read with: the uri literal, or the written
+     * expression when the value is computed. The value is the provider
+     * workspace name. This is deployment knowledge, so it comes from the
+     * pack's own per-project config rather than from the library.
+     */
+    graphqlClientBindings?: Record<string, string>;
+    /**
+     * Which service the operations in a set of files talk to, for a
+     * project whose one frontend uses two clients. A hook call does not
+     * say which client it goes through, so when the sole-client rule
+     * cannot decide, these globs do: an operation whose file matches
+     * gets the entry's workspace. First matching entry wins.
+     */
+    graphqlOperationScopes?: Array<{
+        files: string[];
+        workspace: string;
+    }>;
     /**
      * Per-property-access recognizers, the counterpart to
      * `invocationRecognizers`, firing on `PropertyAccessExpression`
@@ -1356,7 +1421,8 @@ interface DiscoveredCustomUnit {
      */
     channelInfo?: {
         messageBus: MessageBusSemantics["messageBus"];
-        channel: string;
+        /** Null when the pack knows the wire but not the channel on it. */
+        channel: string | null;
     };
     /** The thing that gets deployed and runs this unit, when known. */
     deployableUnit?: DeployableUnit;

package/dist/index.d.ts

@@ -945,6 +945,19 @@ interface ContractPattern {
     paramsExtraction?: {
         property: string;
     };
+    /**
+     * Where the reader finds one endpoint's contract object. Left out,
+     * the ts-rest shape applies: one contract object contains every
+     * endpoint keyed by handler name, and the reader walks up from the
+     * handler to the enclosing router call. With `registrationArgument`,
+     * the zod-openapi shape applies instead: `app.openapi(route, handler)`
+     * passes the endpoint's own contract as the handler's sibling
+     * argument.
+     */
+    endpoint?: {
+        from: "registrationArgument";
+        position: number;
+    };
 }
 type InputMappingPattern = {
     /** Single object parameter, e.g. React Router LoaderFunctionArgs */
@@ -1234,6 +1247,24 @@ interface PatternPack {
      * available without importing anything).
      */
     requiresImport?: string[];
+    /**
+     * Environment variables the pack's library reads from inside
+     * node_modules, where no walk ever looks. Declaring them keeps the
+     * checker from telling a template that a variable is unused when the
+     * library reads it on every invocation. The adapter emits one marker
+     * summary per entry whose `module` some project file imports, and
+     * the runtime-config pairing consults the markers before it accuses.
+     * The module match is a specifier prefix, so one entry covers a
+     * scoped family like `@aws-lambda-powertools/`.
+     */
+    libraryEnvVars?: Array<{
+        /** Module-specifier prefix the library's imports start with. */
+        module: string;
+        /** Env-var name prefixes the library reads, e.g. "POWERTOOLS_". */
+        prefixes?: string[];
+        /** Exact env-var names the library reads. */
+        names?: string[];
+    }>;
     /**
      * Library wrappers that return the function they wrapped. The adapter
      * works this out on its own for a factory inside the project by reading
@@ -1245,6 +1276,40 @@ interface PatternPack {
      * `"Sentry.wrapHandler"`.
      */
     transparentWrappers?: TransparentWrapper[];
+    /**
+     * How this library's client object is constructed, so an operation
+     * summary can say which endpoint its calls go to. Each entry is a
+     * constructor or factory imported from `importModule`, with
+     * `uriProperty` the option key whose value is the endpoint. The
+     * adapter reads every construction in the project and stamps the
+     * client on each operation summary when exactly one distinct client
+     * exists; two or more distinct clients abstain, since a hook call
+     * does not say which one it goes through.
+     */
+    graphqlClients?: Array<{
+        importModule: string;
+        importName: string;
+        uriProperty: string;
+    }>;
+    /**
+     * Which service a client talks to, keyed by the endpoint the
+     * construction was read with: the uri literal, or the written
+     * expression when the value is computed. The value is the provider
+     * workspace name. This is deployment knowledge, so it comes from the
+     * pack's own per-project config rather than from the library.
+     */
+    graphqlClientBindings?: Record<string, string>;
+    /**
+     * Which service the operations in a set of files talk to, for a
+     * project whose one frontend uses two clients. A hook call does not
+     * say which client it goes through, so when the sole-client rule
+     * cannot decide, these globs do: an operation whose file matches
+     * gets the entry's workspace. First matching entry wins.
+     */
+    graphqlOperationScopes?: Array<{
+        files: string[];
+        workspace: string;
+    }>;
     /**
      * Per-property-access recognizers, the counterpart to
      * `invocationRecognizers`, firing on `PropertyAccessExpression`
@@ -1356,7 +1421,8 @@ interface DiscoveredCustomUnit {
      */
     channelInfo?: {
         messageBus: MessageBusSemantics["messageBus"];
-        channel: string;
+        /** Null when the pack knows the wire but not the channel on it. */
+        channel: string | null;
     };
     /** The thing that gets deployed and runs this unit, when known. */
     deployableUnit?: DeployableUnit;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@suss/extractor",
-  "version": "0.5.8",
+  "version": "0.5.10",
   "type": "module",
   "description": "Framework-agnostic extraction pipeline that turns raw extractions into suss behavioral summaries.",
   "keywords": [
@@ -45,7 +45,7 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@suss/behavioral-ir": "0.5.8"
+    "@suss/behavioral-ir": "0.5.10"
   },
   "devDependencies": {
     "tsup": "*",