Bundle Size for the browser version is too big

[moonglum]

We are using Contentful on our site for a few pages like the blog. Unfortunately, the chunk size of contentful keeps increasing version by version (a few versions ago, it was 90kb). It is now at 227kb, and is now the biggest chunk in our entire bundle.

Expected Behavior

• I expect a more reasonable bundle size

Actual Behavior

• It is now by far the biggest dependency we have

Possible Solution

Allow tree shaking instead of including the entire minified bundle. You always get the entire code, I assume that contains a lot of code for previewing etc. which we don't use:

Steps to Reproduce

import {                                                                                                                                                     
      CreateClientParams,                                                                                                                                      
      createClient,                                                                                                                  
} from 'contentful'; 

Context

A bundle size like that is a burden for our customers, who need to download it.

Environment

• Package Version: 10.15.0
• Which API are you using?: Delivery

[moonglum]

I checked our code, as additional information, these are the APIs we are using:

1. We create the client with createClient using the CreateClientParams type.
2. On that client, we only call .withoutUnresolvableLinks.getEntries, .withoutUnresolvableLinks.getEntry, withAllLocales.getEntries and .withAllLocales.getEntry.

[paulcrussell]

Hi @moonglum we've noticed something similar on our project and I thought this PR would most likely resolve it.
#2169

@axe312ger is that your view also?

[axe312ger]

Yes my PR should solve it! :)

[axe312ger]

Its published as v11! Can you rebundle and share your results @moonglum?

It should now properly tree shake :)

[moonglum]

Thanks, Benedikt! Are there any breaking changes? Or do I just keep everything the same?

[axe312ger]

@moonglum The API of the package is the same. We "just" changed the wrapping code. You might need to adjust your requires/imports, but besides of that, everything stayed the same.

Changelog coming soon, preview here: #2334 (comment)

[moonglum]

Thank you, the hint with ESM is important 👍 I'll try it out and get back to you, @axe312ger

[moonglum]

@axe312ger If I update the package, and change nothing else, our build fails:

ERROR in ../node_modules/.pnpm/contentful@11.0.3/node_modules/contentful/dist/contentful.cjs 12:19-32
Module not found: Error: Can't resolve 'os' in '/src/node_modules/.pnpm/contentful@11.0.3/node_modules/contentful/dist'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

The same is raised for zlib and tty. It feels like this uses the node package, and not the browser package. Do I need to adjust the import?

[axe312ger]

The bundle you mentioned is now exported as un-bundled code with all the dependencies. You will be able to deliver smaller files to the browser now, but likely, axios is causing the trouble in your case.

How to Fix the Polyfill Issue:

1. Use Modern Import Syntax

Try using:

import * as contentful from 'contentful';

This could help with modern module resolution and might tell axios to exclude.

2. Fix Your Setup

It looks like you might have an older or misconfigured Webpack 5 setup. Maybe your Next.js version is outdated? Also, older versions of axios can interfere with the bundler picking up the right files. (npm ls or yarn why to the rescue!)

3. Patch Webpack Fallback

If updating your setup doesn’t work, use Webpack’s resolve.fallback to replace these dependencies. Most times, setting it to false works since the dependency is only used in Node related code:

module.exports = {
  resolve: {
    fallback: {
      os: false,
      zlib: false,
      tty: false,
    },
  },
};

This is mostly what axios does in their own webpack (4) config.

If issues persist, here’s a list of shims/polyfills that might help.