Can somebody explain to me why AWS moved away from scoped name like

@aws-cdk

to

aws-cdk-lib

? and also, why some other packages still uses

@aws-cdk

convention? Like

@aws-cdk/aws-apigatewayv2-authorizers-alpha

. Also, how they decide what to put inside

aws-cdk-lib

and what to put outside? It’s hard to track imports from the SST docs due this package segregation. Some examples doesn’t have all the

import

on top. I’m migrating from SST v0.55 to v1.1.1 and it’s driving me crazy 😂 .

I think the idea was if you just have a single package with all the CDK constructs it's simpler so people just need to install one thing and have access to everything

I see, yes, should be easier having all into 1.

we do have an

sst add-cdk

command to add the right version but it's hard to keep that updated with all the different package manager setups people have

But why they are not using the standard

@

thing?

yeah idk why they didn't do

@aws-cdk/core

or whatever

Yeah.

and somehow they claimed the

constructs

package as well, I prefer scoped it's way mroe organized

Yes, that’s so weird.

I think they have plans for

constructs

to become an industry standard so people use that library to make their own cdk based constructs

Yes, I think the same thing.

I'm glad I'm not the only that questions the aesthetics here.

@Dennis Dang haha, same feeling.