AWS Amplify Bundle size seems excessive

[gmzacharydovel]

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework

Not applicable, Web Components

Amplify APIs

Authentication

Amplify Version

v6

Amplify Categories

auth

Backend

Amplify Gen 2

Environment information

Hello, I'm playing with using Amplify for authentication since Cognito supports so many options. Once concern I have is that the library seems to be larger than the rest of my app for the frontend/typescript. The total seems to be 120kb (see screenshot) when I am literally just using the login/refresh/challenge parts of the library.

It might be worth a development cycle to try to figure out how to reduce the size of the bundle of the core authentication logic. I can't help but thing a lot of unneeded stuff is pulled in but can't be tree shaken for some reason.

These are my current amplify imports:

import { Amplify } from "aws-amplify";
import { fetchAuthSession, getCurrentUser } from "aws-amplify/auth";
import {
  confirmResetPassword,
  confirmSignIn,
  confirmSignUp,
  resetPassword,
  signIn,
  signOut,
  signUp,
  updatePassword,
} from "aws-amplify/auth/cognito";

It doesn't seem that amplify supports default imports which can do a lot to help with this kind of bundle size.

Example:

import fetchAuthSession from "aws-amplify/auth/fetchAuthSession";

My amplify version:

"aws-amplify": "^6.15.4"

Thank you in advance!

Describe the bug

Hello, I'm playing with using Amplify for authentication since Cognito supports so many options. Once concern I have is that the library seems to be larger than the rest of my app for the frontend/typescript. The total seems to be 120kb (see screenshot) when I am literally just using the login/refresh/challenge parts of the library.

It might be worth a development cycle to try to figure out how to reduce the size of the bundle of the core authentication logic. I can't help but thing a lot of unneeded stuff is pulled in but can't be tree shaken for some reason.

Expected behavior

I would expect the bundle size to below 10kb. It's more like 120k.

Reproduction steps

Use the typescript version of amplify in a project. Bundle with esbuild.

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line

aws-exports.js

No response

Manual configuration

No response

Additional configuration

No response

Mobile Device

No response

Mobile Operating System

No response

Mobile Browser

No response

Mobile Browser Version

No response

Additional information and screenshots

No response

[gmzacharydovel]

[Simone319]

Thanks @gmzacharydovel for creating this issue. We will look into it and provide an update.

[gmzacharydovel]

I'm importing more of the methods now, and my bundle size is up to ~140k. So it definitely isn't importing everything, but it still is pretty large for a login/auth library.

[Simone319]

Hi @gmzacharydovel,

After reviewing the details, we found some other discussions that may be closely related:

#13501: Very large bundle sizes in V6? This issue reports a similar problem with excessive bundle sizes in Amplify V6. Can you check if the solution provided in that issue works for you?

[gmzacharydovel]

I'll take a look, thank you

[gmzacharydovel]

The size I am seeing isn't anywhere as as large as that. (I think 1/4th?) esbuild also isn't as configurable as webpack to have that kind of issue.

I think this is just generally a large library for some reason. I may try to look deeper at some point.

I try to avoid large libraries like react router as well which I just removed. I think 120KB might seem small to people nowadays.

[ahmedhamouda78]

Hello @gmzacharydovel, I created a bundle using the same imports you have using esbuild, but I am only seeing a size of 33.22kb with all dependencies, minified and gzipped. Can you confirm if the size you are seeing is the compressed package's size or the uncompressed one?