Typescript suddenly incompatible between SST and CDK constructs about sst

[jayair]

Make sure your CDK versions match what sst version prints?

[splicebison]

@jayair @louismorgan-linaro

This is due to aws-cdk-lib being installed twice with two different versions. Scoped @aws-cdk/* libs have a dependency on ^2.110.1 whereas the latest version installed is 2.114.0. This is what is causing the conflict.

You can temporarily work around this by setting your resolutions in your package.json file as such:

"resolutions": {
  "aws-cdk-lib": "2.110.1"
},

After, install again and the TS conflicts will go away.

[louismorgan-linaro]

I managed to fix it yesterday by just uninstalling aws-cdk-lib, constructs and sst then reinstalling sst only. It all seems to work but I think when I initiated the repo with create-sst it had aws-cdk-lib explicitly in the package.json file.

Is there any reason why I shouldn't proceed with only sst as an explicit dependency?

[splicebison]

Is there any reason why I shouldn't proceed with only sst as an explicit dependency?

Yes, a few. It's unreliable to others on your team as you're not explicitly setting project dependencies (even if you are solo, please make this a good habit). You are also relying on peer dependencies for app/development functionality. If those peers change one day, it will break your apps.

By using the resolutions prop, it allows you to continue to (correctly) ever-green your project dependencies until peers / other libs catch-up or fix their dependency tree. The resolution can be removed at a later date when it's fixed by the package maintainers. Also, this way, you are then explicitly declaring a dev dependency for dev work that is required within your project.

[splicebison]

@jayair While we're on the topic, sst current has a hard dependency on aws-cdk-lib. It probably makes more sense to have this as a peer dependency or remove it from the docs and create-set (same goes for constructs).

@louismorgan-linaro my previous comment to you was based on the assumption that aws-cdk-lib and constructs were peer dependencies since they are added to the project when using create sst. I looked at the package.json after and realized they are not peers. In that case, relying on only SST is fine however that's up for the maintainers to decide for how to address this moving forward.

[louismorgan-linaro]

Thanks very much for all the info @splicebison !