Skip to content

fix(next-mdx): report unresolved plugin paths#94984

Open
mturac wants to merge 1 commit into
vercel:canaryfrom
mturac:fix/issue-94118-mdx-loader-error
Open

fix(next-mdx): report unresolved plugin paths#94984
mturac wants to merge 1 commit into
vercel:canaryfrom
mturac:fix/issue-94118-mdx-loader-error

Conversation

@mturac

@mturac mturac commented Jun 20, 2026

Copy link
Copy Markdown

Summary

Closes #94118.

  • forward MDX plugin resolution failures to the webpack loader callback
  • include the unresolved plugin name in the surfaced build error
  • add coverage for missing string plugin paths without changing the existing happy-path fixture

Tests

  • pnpm build-all
  • node --check packages/next-mdx/mdx-js-loader.js
  • pnpm prettier --check packages/next-mdx/mdx-js-loader.js test/e2e/app-dir/mdx/mdx.test.ts
  • pnpm --filter @next/mdx pack-for-isolated-tests
  • git diff --check
  • HEADLESS=true pnpm test-start-webpack test/e2e/app-dir/mdx/mdx.test.ts -t "should report unresolved string plugin paths during build"
  • HEADLESS=true pnpm test-start-webpack test/e2e/app-dir/mdx/mdx.test.ts
  • HEADLESS=true pnpm test-start-turbo test/e2e/app-dir/mdx/mdx.test.ts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

@next/mdx: unhandled promise rejection when plugin path fails to resolve in mdx-js-loader

1 participant