@suss/contract-serverless 0.33.0 → 0.34.0

package/README.md

@@ -1,12 +1,12 @@
 # @suss/contract-serverless
 
-Part of [suss](https://github.com/nimbuscloud-ai/suss), which reads both sides of every call in a repository and says where the two disagree.
+Part of [suss](https://github.com/nimbuscloud-ai/suss), which reads both sides of every call in a repository and reports where the two disagree.
 
-Generate suss `BehavioralSummary[]` from a [Serverless Framework](https://www.serverless.com/framework/docs) service file. A `serverless.yml` deploys working Lambdas, and before this reader existed suss saw none of them: no deployable unit, no environment contract, no event wiring.
+This package builds suss `BehavioralSummary[]` from a [Serverless Framework](https://www.serverless.com/framework/docs) service file. A `serverless.yml` deploys working Lambdas, and before this reader existed suss could not see any of them. It had no deployable unit, environment contract or event wiring for them.
 
 ## What this package is
 
-The framework compiles a service file into one CloudFormation stack. Each function becomes a Lambda, each event becomes the resource that triggers it, and the `resources:` block is copied in as written. So this reader restates the service in SAM's form and hands that to [`@suss/contract-cloudformation`](../cloudformation/), rather than growing a second set of summary builders that would drift from it. A queue wired in a serverless.yml and the same queue wired in a SAM template come out as the same summary.
+The framework compiles a service file into one CloudFormation stack. Each function becomes a Lambda, each event becomes the resource that triggers it, and the `resources:` block is copied in as written. So this reader rewrites the service in SAM's form and passes it to [`@suss/contract-cloudformation`](../cloudformation/), instead of adding a second set of summary builders that would drift away from that package's. A queue wired in a serverless.yml and the same queue wired in a SAM template come out as the same summary.
 
 | Service file | What it becomes |
 |---|---|
@@ -22,15 +22,15 @@ The framework compiles a service file into one CloudFormation stack. Each functi
 
 ## Variables
 
-`${self:...}` points at a path inside the same document, so it resolves here, fallback and all. Every other source (`env:`, `opt:`, `cf:`, `ssm:`, `param:`, `file(...)`, and whatever a plugin registers) refers to a value that a deploy supplies, so the reader keeps the reference as a symbolic token instead of resolving it, guessing at it, or dropping it: an `sqs` event whose ARN is `${env:AUDIT_QUEUE_ARN}` gets the channel `env:AUDIT_QUEUE_ARN`. The token says which binding would ground the boundary, where a null would only say that the wiring is specified somewhere else.
+`${self:...}` points at a path inside the same document, so the reader resolves it, fallback included. Every other source (`env:`, `opt:`, `cf:`, `ssm:`, `param:`, `file(...)`, and anything a plugin registers) refers to a value a deploy supplies. For those, the reader keeps the reference as a symbolic token. It does not resolve it, guess at it or drop it. An `sqs` event whose ARN is `${env:AUDIT_QUEUE_ARN}` gets the channel `env:AUDIT_QUEUE_ARN`. The token shows which binding would ground the boundary, where a null would only show that the wiring is set somewhere else.
 
 A fallback resolves only for a `self:` reference, where the document states both sides. `${opt:region, 'us-east-1'}` stays symbolic, because the document does not state which way an invocation went.
 
-The framework resolves its variables across the whole document before it compiles anything, so the `resources:` block goes through the same resolver: a table written `TableName: ${self:custom.tableName}` is a name by the time CloudFormation sees it, not the reference text. One reference is left exactly as written there: the one whose source is not the framework's. `Fn::Sub` writes `${AWS::Region}` in the same syntax, and rewriting it would turn an intrinsic that the document meant into a token that nothing resolves.
+The framework resolves its variables across the whole document before it compiles anything, so the `resources:` block goes through the same resolver. A table written `TableName: ${self:custom.tableName}` is a name by the time CloudFormation sees it, and no longer the reference text. One kind of reference is left exactly as written there: one whose source is outside the framework. `Fn::Sub` writes `${AWS::Region}` in the same syntax, and rewriting it would turn an intrinsic the document meant into a token that nothing resolves.
 
 ## Two documents, one service
 
-The functions block and the `resources:` block deploy into a single stack, so a logical id means the same thing in both and a queue declared under `resources:` is the queue an `sqs` event points at. They have different provenance labels, built the way a nested stack's label is: `serverless:services/orders/serverless.yml` and `serverless:services/orders/serverless.yml#resources`. A reader can tell which block declared what, and the flow walk still scopes both to one service, since it scopes on the part before the `#`. The label says where the service file lives in the repository, so a monorepo full of services keeps them apart.
+The functions block and the `resources:` block deploy into one stack. A logical id means the same thing in both, and a queue declared under `resources:` is the queue an `sqs` event points at. The two get different provenance labels, built the same way as a nested stack's label: `serverless:services/orders/serverless.yml` and `serverless:services/orders/serverless.yml#resources`. So a reader can tell which block declared what, and the flow walk still scopes both to one service, since it scopes on the part before the `#`. The label includes where the service file is in the repository, so a monorepo full of services keeps them apart.
 
 ## Minimal usage
 
@@ -49,26 +49,26 @@ From the CLI:
 suss contract --from serverless serverless.yml -o service.json
 ```
 
-## What it abstains on, and says so
+## What it does not read, and how it reports that
 
-Each of these writes a line to stderr giving the function, the block, and what stopped the read, so wiring that nobody read is never mistaken for wiring that nobody wrote. Pass `onUnread` to collect them instead.
+Each of these prints a line to stderr with the function, the block, and what stopped the read, so wiring that nobody read is never mistaken for wiring that nobody wrote. Pass `onUnread` to collect them instead.
 
-- **Plugins.** A service that loads plugins is reported once. A plugin can add, rename, or rewrite functions and events, and what it declares is not in the document.
-- **A service file that is a program.** The reader recognizes a `serverless.ts` or `serverless.js` and reports it: a program declares the service, and a reader does not run one to find out what it says. When a directory has a parseable service file alongside one of these, the reader reads the parseable one, the way the framework prefers it. A path with no service file at all is an error, since the caller pointed at it.
-- **Event kinds outside the list above.** `kinesis`, `stream`, `alb`, `websocket`, `cognitoUserPool`, and the rest are reported, not dropped.
-- **A route whose method or path a deploy supplies.** A path such as `/${env:PREFIX}/orders` describes no route this document states, and a token substituted into a path would pair with a route nobody wrote. The rest of the function's events still read.
-- **A handler the document does not state.** The function is skipped: nothing says which code runs it.
+- **Plugins.** A service that loads plugins is reported once. A plugin can add, rename or rewrite functions and events, and what it declares is not in the document.
+- **A service file that is a program.** The reader recognizes a `serverless.ts` or `serverless.js` and reports it. A program declares the service, and the reader does not run one to find out what it declares. When a directory has a parseable service file next to one of these, the reader reads the parseable one, which is also the one the framework prefers. A path with no service file at all is an error, since the caller pointed at it.
+- **Event kinds outside the list above.** `kinesis`, `stream`, `alb`, `websocket`, `cognitoUserPool` and the rest are each reported.
+- **A route whose method or path a deploy supplies.** A path such as `/${env:PREFIX}/orders` does not describe any route this document states, and a token substituted into a path would pair with a route nobody wrote. The function's other events are still read.
+- **A handler the document does not state.** The function is skipped, because nothing shows which code runs it.
 
 ## Limitations (v0)
 
-- **Code scope is the service directory.** The framework packages the whole service into every function's artifact unless `package.individually` narrows it per function, which this reader does not read. A service that sets it gets a scope wider than what deploys.
-- **`provider.region` is read and left symbolic.** No boundary keys on a region today.
-- **Cross-block routing is not composed.** An EventBridge rule declared under `resources:` that targets a queue an `sqs` event drains does not lend the consumer its subject, the way it would inside one CloudFormation template. Each block is read as its own document.
-- **`stage` and multi-stage overrides are not applied.** A value that differs per stage comes out as whatever the document states, with no stage bound.
+- **Code scope is the service directory.** The framework packages the whole service into every function's artifact unless `package.individually` narrows it per function, and this reader does not read that setting. A service that sets it gets a scope wider than what deploys.
+- **`provider.region` is read and left symbolic.** No boundary is keyed on a region today.
+- **Routing across the two blocks is not combined.** An EventBridge rule declared under `resources:` that targets a queue an `sqs` event drains does not give the consumer its subject, as it would inside one CloudFormation template. Each block is read as its own document.
+- **`stage` and overrides per stage are not applied.** A value that differs per stage comes out as whatever the document states, with no stage bound.
 
 ## Where it fits in suss
 
-Depends on `@suss/contract-cloudformation` (which owns every summary builder this reader reaches), `@suss/manifest-aws` (for the CloudFormation intrinsic tags the `resources:` block uses), `@suss/behavioral-ir`, and `yaml`.
+The package depends on `@suss/contract-cloudformation`, which contains every summary builder this reader uses, on `@suss/manifest-aws` for the CloudFormation intrinsic tags the `resources:` block uses, on `@suss/behavioral-ir`, and on `yaml`.
 
 ## More
 

package/dist/index.d.cts

@@ -1,6 +1,19 @@
 import { CloudFormationTemplate } from '@suss/manifest-aws';
 import { BehavioralSummary } from '@suss/behavioral-ir';
 
+/**
+ * Finding and parsing a Serverless Framework service file.
+ *
+ * The framework reads `serverless.yml`, `serverless.yaml`,
+ * `serverless.json` and `serverless.ts`, in that order. This reader
+ * parses the YAML and JSON files. A `.ts` or `.js` service file is a
+ * program, so the reader reports it and does not run it.
+ *
+ * The `resources:` block contains raw CloudFormation, so the parse
+ * registers the CloudFormation intrinsic tags. A serverless.yml usually
+ * writes the full form (`Fn::GetAtt: [Q, Arn]`), and the short form
+ * works too.
+ */
 /** One entry in a function's `events` list, as written. */
 type ServerlessEvent = Record<string, unknown>;
 /** One entry of the `functions` block, as written. */
@@ -21,9 +34,9 @@ interface ServerlessDocument {
     resources?: Record<string, unknown>;
     [key: string]: unknown;
 }
-/** In the framework's own order of preference. */
+/** The parseable service file names, in the framework's order of preference. */
 declare const SERVICE_FILE_NAMES: readonly ["serverless.yml", "serverless.yaml", "serverless.json"];
-/** Recognized in order to be reported rather than read. */
+/** Service files that are programs. The reader reports these and does not run them. */
 declare const PROGRAM_SERVICE_FILE_NAMES: readonly ["serverless.ts", "serverless.js"];
 type ServiceLocation = {
     kind: "readable";
@@ -35,9 +48,9 @@ type ServiceLocation = {
     kind: "missing";
 };
 /**
- * A path that points at a file is taken as that file. A directory is
- * searched parseable spellings first, so a service with both a yml and
- * a ts is read from the yml.
+ * A path to a file is used as it is. A directory is searched for the
+ * parseable files first, so a service with both a yml and a ts file is
+ * read from the yml.
  */
 declare function locateServiceFile(candidate: string): ServiceLocation;
 /** Null when the path contains no service file this reader can parse. */
@@ -45,9 +58,24 @@ declare function findServiceFile(candidate: string): string | null;
 /** Throws when the file is missing or does not parse to an object. */
 declare function loadServerlessDocument(servicePath: string): ServerlessDocument;
 
+/**
+ * A Serverless Framework service, rewritten as the CloudFormation
+ * resources it deploys, for the CloudFormation reader to summarize.
+ *
+ * `provider.environment` becomes SAM's `Globals.Function.Environment`.
+ * Both give every function a default that its own block can override,
+ * so an inherited variable gets `globals` provenance, which fits a
+ * variable written once for the whole service. `provider.runtime` and
+ * the service directory become `Globals.Function.Runtime` and `CodeUri`.
+ *
+ * A function's identity is the key it is written under. People type
+ * that key to deploy, invoke or tail the function, and the framework
+ * builds its logical id from it.
+ */
+
 /** A wiring the document declares that this reader did not translate. */
 interface UnreadWiring {
-    /** Null for a service-level abstention. */
+    /** Null when the wiring belongs to the whole service. */
     functionName: string | null;
     /** The event kind as the framework spells it, or the block name. */
     kind: string;
@@ -62,6 +90,20 @@ interface TranslatedService {
 }
 declare function translateService(document: ServerlessDocument): TranslatedService;
 
+/**
+ * The Serverless Framework's `${...}` variable syntax, resolved as far
+ * as the document itself allows.
+ *
+ * `${self:...}` points inside the same document, so it resolves here.
+ * Every other source, such as `env:` or `ssm:`, gets its value at deploy
+ * time, so the reference stays as a symbolic token: the reference text
+ * without the `${}` wrapper. `env:AUDIT_QUEUE_ARN` tells a reader what
+ * to look up, where null would only say the value is set elsewhere.
+ *
+ * A fallback applies only to a `self:` reference. The framework uses a
+ * deploy-time fallback only when the CLI supplies nothing, and the
+ * document cannot say whether it did.
+ */
 /** A symbolic token is the reference text as written, minus the wrapper. */
 type ResolvedString = {
     kind: "resolved";
@@ -80,18 +122,37 @@ type ResolvedValue = {
 };
 /** Resolves `${...}` references against one parsed serverless.yml document. */
 interface VariableResolver {
-    /** A whole `${self:...}` reference resolves to whatever is at that
-     * path, object or scalar. */
+    /**
+     * A whole `${self:...}` reference resolves to whatever is at that path,
+     * object or scalar.
+     */
     resolveValue(raw: unknown): ResolvedValue;
-    /** A whole reference resolving to an object or array is symbolic, since no string was stated. */
+    /**
+     * A whole reference that resolves to an object or array comes back
+     * symbolic, since the document states no string there.
+     */
     resolveString(raw: string): ResolvedString;
-    /** A reference to anything the framework does not define is left
-     * exactly as written. */
+    /**
+     * Resolves every string in a tree. A reference whose source the
+     * framework does not define, such as `${AWS::Region}` inside an
+     * `Fn::Sub`, is left exactly as written.
+     */
     resolveTemplateTree(value: unknown): unknown;
 }
 declare function createVariableResolver(document: Record<string, unknown>): VariableResolver;
 
-/** A SAM `Events` entry, which is what the CloudFormation reader consumes. */
+/**
+ * Translates one function's `events` list into the SAM event entries
+ * the CloudFormation reader reads.
+ *
+ * Each event kind maps onto the resource the framework compiles it
+ * into, so a serverless.yml and a SAM template with the same wiring
+ * produce the same summary. When this reader does not translate an
+ * event, the reason goes back to the caller, which reports it, so a
+ * wiring nobody read is never mistaken for one nobody wrote.
+ */
+
+/** A SAM `Events` entry, in the form the CloudFormation reader reads. */
 interface SamEvent {
     Type: string;
     Properties?: Record<string, unknown>;
@@ -110,15 +171,35 @@ interface EventContext {
 /** Keyed by the name the framework's own schema uses for each event kind. */
 declare const EVENT_TRANSLATIONS: Record<string, (raw: unknown, ctx: EventContext) => EventTranslation>;
 
+/**
+ * @suss/contract-serverless: behavioral summaries from a Serverless
+ * Framework service file.
+ *
+ * This reader rewrites the service as SAM resources and passes them to
+ * @suss/contract-cloudformation, so a service file and a SAM template
+ * with the same wiring produce the same summaries.
+ *
+ * The functions block and the `resources:` block deploy into one stack
+ * but are read as two documents, labelled `serverless:<file>` and
+ * `serverless:<file>#resources` the way a nested stack is, so the flow
+ * walk still scopes both to one service. The README maps each block to
+ * what it becomes.
+ */
+
 interface ServerlessToSummariesOptions {
     /** Override the logical source file recorded on each summary. */
     source?: string;
-    /** Called once per wiring the reader did not translate. Defaults to
-     * printing a line on stderr. */
+    /**
+     * Called once for each wiring the reader did not translate. Defaults to
+     * printing a line on stderr.
+     */
     onUnread?: (wiring: UnreadWiring) => void;
 }
 declare function serverlessToSummaries(document: ServerlessDocument, options?: ServerlessToSummariesOptions): BehavioralSummary[];
-/** The path may be the service file itself or the directory it is in. */
+/**
+ * Reads a service file and returns its summaries. The path may be the
+ * service file itself or the directory it is in.
+ */
 declare function serverlessFileToSummaries(servicePath: string, options?: ServerlessToSummariesOptions): BehavioralSummary[];
 
 export { EVENT_TRANSLATIONS, PROGRAM_SERVICE_FILE_NAMES, type ResolvedString, type ResolvedValue, SERVICE_FILE_NAMES, type ServerlessDocument, type ServerlessEvent, type ServerlessFunctionDefinition, type ServerlessToSummariesOptions, type ServiceLocation, type TranslatedService, type UnreadWiring, type VariableResolver, createVariableResolver, findServiceFile, loadServerlessDocument, locateServiceFile, serverlessFileToSummaries, serverlessToSummaries, translateService };

package/dist/index.d.ts

@@ -1,6 +1,19 @@
 import { CloudFormationTemplate } from '@suss/manifest-aws';
 import { BehavioralSummary } from '@suss/behavioral-ir';
 
+/**
+ * Finding and parsing a Serverless Framework service file.
+ *
+ * The framework reads `serverless.yml`, `serverless.yaml`,
+ * `serverless.json` and `serverless.ts`, in that order. This reader
+ * parses the YAML and JSON files. A `.ts` or `.js` service file is a
+ * program, so the reader reports it and does not run it.
+ *
+ * The `resources:` block contains raw CloudFormation, so the parse
+ * registers the CloudFormation intrinsic tags. A serverless.yml usually
+ * writes the full form (`Fn::GetAtt: [Q, Arn]`), and the short form
+ * works too.
+ */
 /** One entry in a function's `events` list, as written. */
 type ServerlessEvent = Record<string, unknown>;
 /** One entry of the `functions` block, as written. */
@@ -21,9 +34,9 @@ interface ServerlessDocument {
     resources?: Record<string, unknown>;
     [key: string]: unknown;
 }
-/** In the framework's own order of preference. */
+/** The parseable service file names, in the framework's order of preference. */
 declare const SERVICE_FILE_NAMES: readonly ["serverless.yml", "serverless.yaml", "serverless.json"];
-/** Recognized in order to be reported rather than read. */
+/** Service files that are programs. The reader reports these and does not run them. */
 declare const PROGRAM_SERVICE_FILE_NAMES: readonly ["serverless.ts", "serverless.js"];
 type ServiceLocation = {
     kind: "readable";
@@ -35,9 +48,9 @@ type ServiceLocation = {
     kind: "missing";
 };
 /**
- * A path that points at a file is taken as that file. A directory is
- * searched parseable spellings first, so a service with both a yml and
- * a ts is read from the yml.
+ * A path to a file is used as it is. A directory is searched for the
+ * parseable files first, so a service with both a yml and a ts file is
+ * read from the yml.
  */
 declare function locateServiceFile(candidate: string): ServiceLocation;
 /** Null when the path contains no service file this reader can parse. */
@@ -45,9 +58,24 @@ declare function findServiceFile(candidate: string): string | null;
 /** Throws when the file is missing or does not parse to an object. */
 declare function loadServerlessDocument(servicePath: string): ServerlessDocument;
 
+/**
+ * A Serverless Framework service, rewritten as the CloudFormation
+ * resources it deploys, for the CloudFormation reader to summarize.
+ *
+ * `provider.environment` becomes SAM's `Globals.Function.Environment`.
+ * Both give every function a default that its own block can override,
+ * so an inherited variable gets `globals` provenance, which fits a
+ * variable written once for the whole service. `provider.runtime` and
+ * the service directory become `Globals.Function.Runtime` and `CodeUri`.
+ *
+ * A function's identity is the key it is written under. People type
+ * that key to deploy, invoke or tail the function, and the framework
+ * builds its logical id from it.
+ */
+
 /** A wiring the document declares that this reader did not translate. */
 interface UnreadWiring {
-    /** Null for a service-level abstention. */
+    /** Null when the wiring belongs to the whole service. */
     functionName: string | null;
     /** The event kind as the framework spells it, or the block name. */
     kind: string;
@@ -62,6 +90,20 @@ interface TranslatedService {
 }
 declare function translateService(document: ServerlessDocument): TranslatedService;
 
+/**
+ * The Serverless Framework's `${...}` variable syntax, resolved as far
+ * as the document itself allows.
+ *
+ * `${self:...}` points inside the same document, so it resolves here.
+ * Every other source, such as `env:` or `ssm:`, gets its value at deploy
+ * time, so the reference stays as a symbolic token: the reference text
+ * without the `${}` wrapper. `env:AUDIT_QUEUE_ARN` tells a reader what
+ * to look up, where null would only say the value is set elsewhere.
+ *
+ * A fallback applies only to a `self:` reference. The framework uses a
+ * deploy-time fallback only when the CLI supplies nothing, and the
+ * document cannot say whether it did.
+ */
 /** A symbolic token is the reference text as written, minus the wrapper. */
 type ResolvedString = {
     kind: "resolved";
@@ -80,18 +122,37 @@ type ResolvedValue = {
 };
 /** Resolves `${...}` references against one parsed serverless.yml document. */
 interface VariableResolver {
-    /** A whole `${self:...}` reference resolves to whatever is at that
-     * path, object or scalar. */
+    /**
+     * A whole `${self:...}` reference resolves to whatever is at that path,
+     * object or scalar.
+     */
     resolveValue(raw: unknown): ResolvedValue;
-    /** A whole reference resolving to an object or array is symbolic, since no string was stated. */
+    /**
+     * A whole reference that resolves to an object or array comes back
+     * symbolic, since the document states no string there.
+     */
     resolveString(raw: string): ResolvedString;
-    /** A reference to anything the framework does not define is left
-     * exactly as written. */
+    /**
+     * Resolves every string in a tree. A reference whose source the
+     * framework does not define, such as `${AWS::Region}` inside an
+     * `Fn::Sub`, is left exactly as written.
+     */
     resolveTemplateTree(value: unknown): unknown;
 }
 declare function createVariableResolver(document: Record<string, unknown>): VariableResolver;
 
-/** A SAM `Events` entry, which is what the CloudFormation reader consumes. */
+/**
+ * Translates one function's `events` list into the SAM event entries
+ * the CloudFormation reader reads.
+ *
+ * Each event kind maps onto the resource the framework compiles it
+ * into, so a serverless.yml and a SAM template with the same wiring
+ * produce the same summary. When this reader does not translate an
+ * event, the reason goes back to the caller, which reports it, so a
+ * wiring nobody read is never mistaken for one nobody wrote.
+ */
+
+/** A SAM `Events` entry, in the form the CloudFormation reader reads. */
 interface SamEvent {
     Type: string;
     Properties?: Record<string, unknown>;
@@ -110,15 +171,35 @@ interface EventContext {
 /** Keyed by the name the framework's own schema uses for each event kind. */
 declare const EVENT_TRANSLATIONS: Record<string, (raw: unknown, ctx: EventContext) => EventTranslation>;
 
+/**
+ * @suss/contract-serverless: behavioral summaries from a Serverless
+ * Framework service file.
+ *
+ * This reader rewrites the service as SAM resources and passes them to
+ * @suss/contract-cloudformation, so a service file and a SAM template
+ * with the same wiring produce the same summaries.
+ *
+ * The functions block and the `resources:` block deploy into one stack
+ * but are read as two documents, labelled `serverless:<file>` and
+ * `serverless:<file>#resources` the way a nested stack is, so the flow
+ * walk still scopes both to one service. The README maps each block to
+ * what it becomes.
+ */
+
 interface ServerlessToSummariesOptions {
     /** Override the logical source file recorded on each summary. */
     source?: string;
-    /** Called once per wiring the reader did not translate. Defaults to
-     * printing a line on stderr. */
+    /**
+     * Called once for each wiring the reader did not translate. Defaults to
+     * printing a line on stderr.
+     */
     onUnread?: (wiring: UnreadWiring) => void;
 }
 declare function serverlessToSummaries(document: ServerlessDocument, options?: ServerlessToSummariesOptions): BehavioralSummary[];
-/** The path may be the service file itself or the directory it is in. */
+/**
+ * Reads a service file and returns its summaries. The path may be the
+ * service file itself or the directory it is in.
+ */
 declare function serverlessFileToSummaries(servicePath: string, options?: ServerlessToSummariesOptions): BehavioralSummary[];
 
 export { EVENT_TRANSLATIONS, PROGRAM_SERVICE_FILE_NAMES, type ResolvedString, type ResolvedValue, SERVICE_FILE_NAMES, type ServerlessDocument, type ServerlessEvent, type ServerlessFunctionDefinition, type ServerlessToSummariesOptions, type ServiceLocation, type TranslatedService, type UnreadWiring, type VariableResolver, createVariableResolver, findServiceFile, loadServerlessDocument, locateServiceFile, serverlessFileToSummaries, serverlessToSummaries, translateService };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@suss/contract-serverless",
-  "version": "0.33.0",
+  "version": "0.34.0",
   "type": "module",
   "description": "Turn a Serverless Framework serverless.yml into a suss contract and check it against the Lambda handlers and clients behind it.",
   "keywords": [
@@ -15,7 +15,7 @@
   ],
   "license": "Apache-2.0",
   "author": "Nimbus Cloud AI LLC",
-  "homepage": "https://github.com/nimbuscloud-ai/suss/tree/main/packages/contract/serverless#readme",
+  "homepage": "https://suss.sh",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nimbuscloud-ai/suss.git",
@@ -48,11 +48,11 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@suss/behavioral-ir": "0.33.0",
-    "@suss/contract-aws-apigateway": "0.33.0",
-    "@suss/contract-cloudformation": "0.33.0",
-    "@suss/ir-core": "0.33.0",
-    "@suss/manifest-aws": "0.33.0",
+    "@suss/behavioral-ir": "0.34.0",
+    "@suss/contract-aws-apigateway": "0.34.0",
+    "@suss/contract-cloudformation": "0.34.0",
+    "@suss/ir-core": "0.34.0",
+    "@suss/manifest-aws": "0.34.0",
     "yaml": "^2.4.0"
   },
   "devDependencies": {