Skip to content

test: add MDX metadata export regression coverage#6

Draft
vercel-gh-bot-2[bot] wants to merge 2 commits into
next-maintainer-agent/base-80fd3fed693bfrom
next-maintainer-agent/issue-91735-02a2a3a3b96c
Draft

test: add MDX metadata export regression coverage#6
vercel-gh-bot-2[bot] wants to merge 2 commits into
next-maintainer-agent/base-80fd3fed693bfrom
next-maintainer-agent/issue-91735-02a2a3a3b96c

Conversation

@vercel-gh-bot-2

@vercel-gh-bot-2 vercel-gh-bot-2 Bot commented Jul 21, 2026

Copy link
Copy Markdown

What

  • Infer the active webpack module layer when a custom rule uses defaultLoaders.babel without an explicit bundleLayer.
  • Preserve the explicit loader option when one is provided.

This lets app-router MDX pages run the React Server Component transform in the server layer, so server-only exports such as metadata are not incorrectly rejected as client exports.

Fixes vercel#91735

Testing

  • pnpm test-start-webpack test/e2e/app-dir/mdx-metadata/mdx-metadata.test.ts
  • pnpm --filter=next build
  • Prettier and ESLint on packages/next/src/build/webpack/loaders/next-swc-loader.ts

Next-Maintainer-Receipt: v1._H172Clhb2n_O7P_YWOFA9aOnbsmzzwXy2_4cQoD3C4
Next-Maintainer-Receipt: v1.p5MoUXKRpVt326KJUPiQu91Gi9mQLWw4ZjBQiPFl2ww
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.

0 participants