Cannot use query parameters in Vite `import.meta.glob`

[joshpensky]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and discussions and couldn’t find anything (or linked relevant results below)

Affected package

@mdx-js/rollup@3.1.1

Steps to reproduce

https://github.com/joshpensky/mdx-js-rollup-vite-glob-repro

1. Create a new Vite 7 project with @mdx-js/rollup@3.1.1
2. Define your vite.config.ts file with the mdx plugin
3. Create a few mdx files, then import with a raw query:

const docs = import.meta.glob("./docs/*.mdx", {
  query: "?raw",
  import: "default",
  eager: true,
});

Actual behavior

The object values in the returned glob object are function components

Expected behavior

The object values should be the raw strings, which is typical behavior for the ?raw query param in Vite

Runtime

node@24.11.0

Package manager

pnpm@10.21.0

Operating system

macOS Sequoia 15.3.2

Build and bundle tools

Vite

[joshpensky]

This looks to have broken in 3.1.1 with the merge of #2629

[wooorm]

Pinging @markdalgleish, as Mark may have some good insights!

[wooorm]

a) is eager needed for MDX? Is it needed for this bug? Never heard of it, but sounds separate?
b) ignoring ? stuff seems good, I get the ?raw case, but what is supporting that? If “that” is some other plugin, shouldn’t that plugin not run before MDX and similar? If there is no raw plugin, do MDX alternatives all each have support for ?raw baked in and should it be in MDX too? Or is it a builtin Vite thing?

[joshpensky]

thanks @wooorm!

a) eager is not needed (it just imports all the modules immediately). The bug still persists without the option
b) ?raw is a built-in Vite feature to import assets as string. This worked fine on 3.1.0, but seems to have broken with that PR

[remcohaszing]

I see how #2629 would trigger this issue. I also understand why this broke your build and why you would expect using a query parameter to work. I do believe however, that it’s the right choice to ignore query parameters in a transformer.

If ?raw is a special case for Vite, I expect Vite to handle it. The MDX plugin shouldn’t receive it. Otherwise the MDX plugin would have to handle every special query parameter Vite or a third party plugin comes up with.

As a side note: Loading MDX in the frontend (almost) implies you intend to compile and evaluate it dynamically in the browser. Evaluating JavaScript in the browser is a dangerous operation and should be avoided if possible.

[joshpensky]

I also expected Vite to handle this automatically. I've also confirmed that changing the plugin ordering does not fix the issue

We've temporarily wrapped this plugin to restore the expected functionality we had before the change in #2629:

const mdxPlugin = mdx();
const rawMdxPlugin: Plugin = {
  ...mdxPlugin,
  transform(code, id) {
    // Skip default MDX transform for raw files (will be handled by Vite)
    if (id.includes('?raw')) return null;

    return mdxPlugin.transform(code, id);
  },
};

[remcohaszing]

I suggest you open an issue in the Vite repo to see what they think.