Unable to import components — "Could not resolve "./Cool""

Thank you for this great library and thank you to all the contributors and example code that has got me to this point.

I am trying to get a proof of concept going, but can’t get past component importing using the cwd option.

I have tried pulling some of the example repositories as well as starting on my own from scratch. I can also reproduce the error in codesandbox.

Is there anything I’m doing incorrectly? Is there some bug in a dependency minor version somewhere? I’m stuck!

• mdx-bundler version: 5.1.0
• next version: 11.0.1
• react version: 17.0.2
• node version: 14.17.3
• npm version: 6.14.13

Relevant code or config

export const getSinglePost = async (slug) => {
  const source = getSourceOfFile(slug);
  const directory = path.join(POSTS_PATH, slug);

  console.log("cwd", directory);

  const { code, frontmatter } = await bundleMDX(source, {
    cwd: directory
  });

  return {
    frontmatter,
    code
  };
};

What you did: Imported a component in the same directory as the .mdx file.

What happened: Got an error,

Error: Build failed with 1 error:
_content/blog/cool/_mdx_bundler_entry_point.mdx:10:17: error: Could not resolve "./Cool"

Reproduction repository: https://codesandbox.io/s/peaceful-violet-5oe07?file=/lib/data/posts.js&initialpath=/blog/cool

[Arcath]

Using 5.1.1 my esbuild has fallen all the way back to 0.8.57 based on the requirements of https://github.com/fal-works/esbuild-plugin-global-external Not sure why our peerDependency of 0.11.x || 0.12.x isnt throwing an issue here.

I’ve opened a PR to sort this hopefully. https://github.com/fal-works/esbuild-plugin-global-externals/pull/3

I am assuming this is the problem as my site now has the same fault after moving from 4.x to 5.x.

[phatnhse]

I got a similar issue and it was resolved in v.5.1.1

Thanks @Arcath 👍