chore: Vite Bundle Size Action Example Demonstrating Vite Errors with library

[ErikCH]

This PR is demonstrate the errors with Vite when running with the amplify-js library.

Description of changes

This adds a Vite app to the bundle-size action directory

Issue #, if available

The errors are seen in #7499

Description of how you validated changes

To reproduce, run yarn dev.
Or
yarn build

[ericclemmons]

Should this use latest? I don't know how this project is initialized, so I'm uncertain if these are latest, next, or specifically defined from some external docs.

[ErikCH]

This is what's configured after a yarn create @vitejs/app

[lgtm-com]

This pull request introduces 3 alerts when merging de50adb into 492f925 - view on LGTM.com

new alerts:

• 3 for Unused variable, import, function or class

[ericclemmons]

yarn dev initially failed for me, then I changed this to:

		<script>
			// https://docs.amplify.aws/start/getting-started/setup/q/integration/angular#angular-6-support
			window.global = window;
		</script>

Now yarn dev works! But yarn build still fails...

[codecov]

Codecov Report

Merging #7970 (468a14c) into main (02d72e6) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #7970   +/-   ##
=======================================
  Coverage   74.25%   74.25%           
=======================================
  Files         215      215           
  Lines       13473    13473           
  Branches     2646     2646           
=======================================
  Hits        10004    10004           
  Misses       3271     3271           
  Partials      198      198           

Impacted Files	Coverage Δ
packages/core/src/Platform/version.ts	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 492f925...468a14c. Read the comment docs.

[ericclemmons]

So we learned the following:

1. @aws-sdk/credential-provider-imds is only required by @aws-sdk/credential-provider-node

2. @aws-sdk/credential-provider-node is defined in runtimeConfig.ts within the @aws-sdk/client-* packages.

3. AWS SDK has a browser field for bundlers to use runtimeConfig.browser.ts instead, but Vite doesn't seem to be respecting this:

   • When importing some modules with multiple entry points in package.json, the server version is selected instead of the browser version vitejs/vite#2329
   • Server version is used in browser when bundled with Vite okta/okta-auth-js#641

My question is, how can we or aws-sdk-js-v3 define exports or something so that Vite picks up on it since it won't respect browser?

[lgtm-com]

This pull request introduces 3 alerts when merging 468a14c into 5af2e1a - view on LGTM.com

new alerts:

• 3 for Unused variable, import, function or class

[ErikCH]

I have uploaded a newer work around, that should allow amplify to work with Vite. See -> https://github.com/aws-amplify/amplify-js/issues/7499#issuecomment-804386820

[lgtm-com]

This pull request introduces 2 alerts when merging 0ac0dc6 into 2b800f5 - view on LGTM.com

new alerts:

• 2 for Unused variable, import, function or class

[ErikCH]

No longer needed, I'll close this.

[github-actions]

This pull request has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels or Discussions for those types of questions.