Tree shaking not working when importing from a component library inside a MDX file

[jimzer]

First of all, thank you for this awesome bundler!

• mdx-bundler version: v8.0.1
• node version: v14.18.1
• yarn version: v1.22.17

Relevant code or config

I use Next JS, here is my bundler configuration

  const { code, frontmatter } = await bundleMDX({
    file: path.resolve(path.join(postPath, 'index.mdx')),
    //cwd: path.resolve(postPath),
    cwd: process.env.PWD,
    esbuildOptions(options) {
      // options.minify = false
      options.target = ['esnext']
      options.platform = 'node'
      options.treeShaking = true
      return options
    },
    xdmOptions(options) {
      options.remarkPlugins = [...(options.remarkPlugins ?? []), remarkMath]
      options.rehypePlugins = [...(options.rehypePlugins ?? []), rehypeMathjax]
      return options
    },
  })

What you did:

I import a library of components into my MDX page like so:

import { Box } from '@components/core'

What happened:

The whole @components/core library is bundled into my web page.

Problem description:

I expected that tree shaking would eliminate all the unused exported components. Is it normal that it did not work? Maybe it's not possible to get the MDX content tree shaked?

[FradSer]

Your question is very similar to https://github.com/kentcdodds/mdx-bundler/issues/165 , you should check it.

[joe-bell]

I've actually noticed that I have a similar experience with local components – unused ones aren't eliminated from the resulting bundle