Reduce size of install

[jimfleming]

Is your feature request related to a problem? Please describe.

A clean install of just two v3 SDK dependencies generates a 200MB node_modules folder.

Minimal package.json:

{
  "dependencies": {
    "@aws-sdk/client-dynamodb": "^3.4.1",
    "@aws-sdk/util-dynamodb": "^3.4.1"
  }
}

Run npm install.

Describe the solution you'd like

Much smaller builds for lambdas. As is, we're just under the 250MB S3 upload limit for lambdas.

Additional context

Screenshot attached of the size breakdown from dust. It looks like the bulk of the install is coming from react-native and android.

[willfarrell]

This is related to #1536

[jimfleming]

As this comment in #1536 noted the issue appears to be caused by upgrading to npm@7.

To revert back to the npm@6 behavior we can use: npm install --legacy-peer-deps. This requires first deleting the package-lock.json and node_modules as it won't remove peer dependencies that were already installed.

Alternatively, we can explicitly omit peer dependencies: npm install --omit peer which will remove existing peer dependencies.

The long-term fix sounds like the peer dependencies should be marked as optional.

[trivikr]

Closing this issue, as the specific problem of react-native getting installed was fixed by asking customers to install react-native polyfills in #2191

Reducing the install size further is being tracked in #2132

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

[trivikr]

Tagging @jimfleming @willfarrell as you had pointed out about install size of v3 in the past.

The AWS SDK for JavaScript team is working on reducing the install size of v3 further.
Please test or create issues on our experimental repo if you have questions/suggestions https://github.com/trivikr/temp-client-s3

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.