Larger bundler size when importing next-firebase-auth than expected?

Describe the bug Seems like there is some issue with bundle size, when importing next-firebase-auth, that leads to a considerably larger bundle size than expected.

In my case “without” using import { … } from ‘next-firebase-auth’; gives a package size for firstload of a page of 75.1kb, then we usinng the imports the size jumps to 143kb - I read elsewhere you should only expect the size to be around 20kb?

Version “next-firebase-auth”: “^0.13.2”

To Reproduce with using next-firebase-auth [username].tsx

...
import initAuth from '../initAuth';
import { AuthAction, AuthUserContext, withAuthUser } from 'next-firebase-auth';
initAuth(); // Required if page uses any auth calls related to next-firebase-auth
....
export default  withAuthUser({
  whenUnauthedBeforeInit: AuthAction.RENDER,
  whenUnauthedAfterInit: AuthAction.RENDER,
})(Profile)

without using next-firebase-auth [username].tsx

....
export default  Profile

[kmjennison]

Thanks for this info. I explored this in the demo app and feel confident the bundle size is mostly Firebase JS.

First load JS for the example app index page:

• With next-firebase-app (NFA): 136kb
• Without NFA: ~66kb – commit https://github.com/gladly-team/next-firebase-auth/commit/53c4eff082679439d634dd506f6d9ede9633b6c5
• Without NFA but with Firebase: 130kb – commit https://github.com/gladly-team/next-firebase-auth/commit/7181cae583192ab94d32091e0ba97607d59a0a85

With NFA:

Without NFA:

Without NFA but with Firebase:

Firebase’s size should be reduced when #164 is implemented.

[krthush]

Cool sounds good, yeah hopefully we’ll get the modular firebase support sometime and then we can further reduce the bundle size impact from firebase.