Expose core as an export

[thdxr]

Currently if you use anything from aws-cdk-lib it causes node to travese this entire package and evaluate every single file which is noticibly slow.

Exposing core will alleviate this for situations where you're just importing things like App or Duration

[gitpod-io]

[TheRealAmazonKendra]

Can you clarify what you mean by "use anything from aws-cdk-lib?"

[thdxr]

If I do import { Duration } from "aws-cdk-lib" that will hit the index file which essentially links to every other file provided by aws-cdk whether you're using it or not.

This causes two issues:

1. Slow to load - I'm seeing 2+ seconds before node can even run user code. This fixes cuts that to 25-30% (more fixes to be done)

2. If you bundle code that includes this the bundle is much larger than it needs to be

Doing import { Duration } from "aws-cdk-lib/core" makes this less of an issue

[mrgrain]

Duplicate of #17986

[thdxr]

Duplicate of #17986

Thanks for pointing that out - I should have searched first

[mrgrain]

Duplicate of #17986

Thanks for pointing that out - I should have searched first

No worries. 😃 It's easy if you know that this has popped up before. There might be more than just this one tbh.

Either way, the issue is important to this discussion. I don't see has having moved away from that position.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: ea3e2ea
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[TheRealAmazonKendra]

Given that we won't be accepting this change at this time, I'm going to go ahead and close this PR.