fix: imports from ESM modules cannot find correct type definitions

[mrgrain]

With #23813 and #23846 we have introduced a new, dedicated export for use in ESM modules. The generated type definitions for this ESM export entry point do not contain the correct types. This is expected, however when TypeScript attempts to use the ESM export, it will fail due to the lack of type definitions.

This change explicitly sets the type definitions for the top-level export to index.d.ts which contains the correct type definitions for all exports, no matter if they are CJS or ESM.

---

All Submissions:

• Have you followed the guidelines in our Contributing guide?

Adding new Construct Runtime Dependencies:

• This PR adds new construct runtime dependencies following the process described here

New Features

• Have you added the new feature to an integration test?
  • Did you use yarn integ to deploy the infrastructure and generate the snapshot (i.e. yarn integ without --dry-run)?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[gitpod-io]

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

✅ Updated pull request passes all PRLinter validations. Dissmissing previous PRLinter review.

[aws-cdk-automation]

AWS CodeBuild CI Report

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

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