SST Satisfies preventing deploy due to linter in SST Typescript

[icon2341]

Recently after deleting our cache in github actions, the SST deploy no longer works because it doesn't like the SST satisfies, how can we proceed? We are unable to migrate to v3 at this moment and would like to get this working in the meantime.

`
import { SSTConfig } from "sst";
import { NextjsSite } from "sst/constructs";
import { AuthStack } from "./stacks/cognitoUserPoolStack";
import { Vpc, SubnetType } from "aws-cdk-lib/aws-ec2";

export default {
config(_input : any) {
return {
name: "...",
region: "us-east-1",
};
},
stacks(app : any) {

app.stack(function Site({ stack } : any) {

  // Alternatively use an existing VPC
  const vpc = Vpc.fromLookup(stack, "Lambda VPC",{ vpcId: "..." });
  const vpcSubnets = {
    subnetType: SubnetType.PRIVATE_WITH_EGRESS,
  };
  
  const site = new NextjsSite(stack, "site",{
    timeout: "30 seconds",
    environment:{

      NEXT_PUBLIC_SUPABASE_ANON_KEY: process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!,
      NEXT_PUBLIC_SUPABASE_URL: process.env.NEXT_PUBLIC_SUPABASE_URL!,
      NEXT_PUBLIC_URL: process.env.NEXT_PUBLIC_URL!,

      AWS_BEDROCK_KEY:process.env.AWS_BEDROCK_KEY!,
      EXCHANGE_KEY:process.env.EXCHANGE_KEY!,
      EXCHANGE_TOKEN:process.env.EXCHANGE_TOKEN!,
      NEXT_PUBLIC_MIXPANEL_TOKEN:process.env.NEXT_PUBLIC_MIXPANEL_TOKEN!, //jarl1111
      COGNITO_DOMAIN:process.env.COGNITO_DOMAIN!,
      COGNITO_APP_CLIENT_ID:process.env.COGNITO_APP_CLIENT_ID!,
      COGNITO_APP_CLIENT_SECRET:process.env.COGNITO_APP_CLIENT_SECRET!,
      COGNITO_AZURE_CLIENT_ID:process.env.COGNITO_AZURE_CLIENT_ID!,
      COGNITO_AZURE_CLIENT_SECRET:process.env.COGNITO_AZURE_CLIENT_SECRET!,
      AZURE_IDENTITY_PROVIDER:process.env.AZURE_IDENTITY_PROVIDER!,
      USER_POOL_ID:process.env.USER_POOL_ID!,
      AUTH0_SECRET:process.env.AUTH0_SECRET!,
      AUTH0_BASE_URL:process.env.AUTH0_BASE_URL!,
      AUTH0_ISSUER_BASE_URL:process.env.AUTH0_ISSUER_BASE_URL!,
      AUTH0_CLIENT_ID:process.env.AUTH0_CLIENT_ID!,
      AUTH0_CLIENT_SECRET:process.env.AUTH0_CLIENT_SECRET!,
      DB_USER_NAME:process.env.DB_USER_NAME!,
      DB_PASSWORD:process.env.DB_PASSWORD!,
      DB_PORT:process.env.DB_PORT!,
      DB_HOST:process.env.DB_HOST!,
      CA_CERT:process.env.CA_CERT!,
      DB_NAME:process.env.DB_NAME!,
      NEXT_PUBLIC_GERTRUDE_URL: process.env.NEXT_PUBLIC_GERTRUDE_URL!,
      ENVIRONMENT_SHORTHAND: process.env.ENVIRONMENT_SHORTHAND!,
      ROSETTA_API_KEY: process.env.ROSETTA_API_KEY!,
      NEXT_PUBLIC_ROSETTA_URL: process.env.NEXT_PUBLIC_ROSETTA_URL!,
    },
    cdk: {
      server: {
        vpc,
        vpcSubnets,
      },
      revalidation: {
        vpc,
        vpcSubnets,
      }
    }
  });

  stack.addOutputs({
    SiteUrl: site.url,
  });
}).stack(AuthStack);

},
} satisfies SSTConfig;

`

`
npx sst deploy --stage dev
(node:90441) NOTE: The AWS SDK for JavaScript (v2) is in maintenance mode.
SDK releases are limited to address critical bug fixes and security issues only.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the blog post at https://a.co/cUPnyil
(Use node --trace-warnings ... to show where the warning was created)
Using stage: dev
Preparing your SST app

Mismatched versions of AWS CDK packages. SST currently supports 2.50.0. Fix using:

npm install [email protected] --save-exact

Learn more about it here — https://docs.sst.dev/known-issues

✘ [ERROR] Expected ";" but found "satisfies"

sst.config.ts:81:2:
  81 │ } satisfies SSTConfig;
     │   ~~~~~~~~~
     ╵   ;

Build failed with 1 error:
sst.config.ts:81:2: ERROR: Expected ";" but found "satisfies"
`

[jayair]

Which version of typescript? And I think for something like this you can just ignore this line for the linter.

[icon2341]

@jayair Hi, thanks for the reply, i should have specified, i am using Version 5.4.5 ("typescript": "^5")

How can I do that?
Thanks!

I have already tried

  // eslint-disable-next-line
} satisfies SSTConfig;

and

// @ts-ignore
} satisfies SSTConfig;

[icon2341]

UPDATE:

was related to sst versioning but not in the way you would expect... sometimes there are additional packages, either related or unrelated to the SST package within npm that can override dependencies which can cause weird problems like this.

Closing but keep an eye out for that, future coders...