fast-xml-parser not listed as a dependency of @aws-sdk/client-s3

[lineape]

Checkboxes for prior research

• I've gone through Developer Guide and API reference
• I've checked AWS Forums and StackOverflow.
• I've searched for previous similar issues and didn't find any solution.

Describe the bug

@aws-sdk/client-s3 3.529.0 no longer lists fast-xml-parser as a dependency, even though it's used at runtime (and is not bundled in the compiled javascript).

This causes module not found errors.

SDK version number

@aws-sdk/client-s3@3.529.0

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

v18.19.1

Reproduction Steps

mkdir test && cd test
npm init -y && npm add @aws-sdk/client-s3
echo 'new require("@aws-sdk/client-s3").S3Client();' > test.js
node test.js

Observed Behavior

node:internal/modules/cjs/loader:1137
throw err;
^

Error: Cannot find module 'fast-xml-parser'

Expected Behavior

No errors

Possible Solution

Re-add fast-xml-parser to dependencies or bundle fast-xml-parser with build.

Additional Information/Context

No response

[kuhe]

Hi, I'm sorry for releasing this bug. Our validation scripts have a gap in checking external dependencies, which I'll work on a patch for.

As a workaround, please use the previous version or add fast-xml-parser@4.2.5 to your application temporarily.

[diegodleon]

No prob! Thanks for the quick fix, any ETAs on the release of the fix? @kuhe

[alex-at-cascade]

Should probably check all clients for which ones actually reference it. In my case it was client-lambda, but i had actually been getting the package incidentally from client-sts (since it had apparently been removed from, or had never been added to, client-lambda some time ago).

[trivikr]

We're aiming to get this issue fixed in future release https://github.com/aws/aws-sdk-js-v3/releases/tag/v3.529.1
Expected time of release as of this comment is around 5 PM Pacific, i.e. in two hours.

[tdq132]

I ran into the same issue when using client-ec2 via a CDK Custom Resource.
Workaround for me was to add this to cdk.json context: "@aws-cdk/customresources:installLatestAwsSdkDefault": false