I’m doing migration from 0.55 to 1.0.0… Can I still use classes? or I need to migrate all my classes into functions?

you can still use classes!

Is there any example?

Hm that's probably unrelated to class vs functional

Looks like is expecting Construct?

Uhh.. My

scope

parameters are still

<http://sst.App|sst.App>

in v1

Mmm.

I'm still on v1.0.4.

Ah, maybe that changed after.

Code snippet:

import * as sst from "@serverless-stack/resources";
import { Stack, StackProps } from "@serverless-stack/resources";
import { RemovalPolicy } from "aws-cdk-lib";
import { Bucket, BucketEncryption } from "aws-cdk-lib/aws-s3";
import { Table } from "aws-cdk-lib/aws-dynamodb";
import DynamoDBTable from "./dynamodb-table.construct";

export interface DataStackProps extends StackProps {
  isEphemeralStage: boolean;
}

/**
 * Stack to hold persistent data:
 * - DynamoDB table(s)
 * - Data Lake
 */
export default class DataStack extends Stack {
  public readonly primaryTable: Table;
  public readonly dataLakeBucket: Bucket;

  constructor(scope: <http://sst.App|sst.App>, id: string, props: DataStackProps) {
    super(scope, id, props);

I have to do a migration from

0.x

, so planning to migrate to the latest.

Oh of course. Things move fast here. I'm behind because I haven't updated in a week!

Yeah.

Yup, I'm still using class too. (Wouldn't call it OOP , just classes.)

True.

Hey @Adrián Mouly just check if you are still the issue. v0.55 is quite old. Can you try updating to v0.59.0 first? We made the CDK v1 to v2 update with a few breaking changes.

Construct is fragile. The jump to 10.1.x from 10.0.x can create the errors above. (I was just fighting with this surprise, on a build that had no SST/CDK changes)