George Fu

A fix was released today that allows bucket inputs to serve as request endpoints. ```ts const s3 = new S3({ region: "us-west-2", bucketEndpoint: true, }); const get = await s3.getObject({...

A fix is expected later today in the next release. The release notes will include mention of the #5843 pull request "fix(lib-storage): use AbortController interface instead of class as type".

In our CJS distribution for `@aws-sdk/client-dynamodb`, which is what we expect react-native to use for reasons originating in the metro bundler, we have the following platform specific files ``` /dist-cjs/runtimeConfig.js...

if we drop support for TS3.4, do should customers downlevel types themselves or simply upgrade their TS version?

A fix was released today that allows bucket inputs to serve as request endpoints. https://github.com/aws/aws-sdk-js-v3/releases/tag/v3.525.0 https://www.npmjs.com/package/@aws-sdk/client-s3/v/3.525.0 See https://github.com/aws/aws-sdk-js-v3/issues/4394 for example.

@perpil in https://github.com/aws/aws-sdk-js-v3/releases/tag/v3.499.0, we released dynamic imports (lazy loading) for the node credential chain providers. SSO and other credential providers including their dependency clients will not be loaded if you...

We can check what is loaded by logging the require.cache. We have additional updates pending to defer both the providers and the underlying clients used by providers, such as SSO,...

https://github.com/aws/aws-sdk-js-v3/pull/5681 contains a second phase of implementing deferred loading.

> need to mark packages as external This shouldn't be necessary. With the introduction of async imports, bundlers should generate the unused code into separate chunks that are never loaded....

I see, it's not supported at the same level as in webpack. In that case marking external for esbuild is a good way to induce the splitting.