@vitejs/plugin-react can support more extensions

[LaamGinghong]

Clear and concise description of the problem

I'm doing markdown conversion to React component. However, this plugin may only be supported .jsx? or .tsx? file. So I had to use an extra Babel plugin to handle the files generated by the markdown transformation.

Suggested solution

Add a configuration extension to the plugin's options and support any text that conforms to React component.

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[Niputi]

please give more details.
what exactly are you trying to do and how do you expect it to work

[LaamGinghong]

@Niputi
I wrote a Vite plugin to transform markdown to React component. The output of the plugin looks something like this:

export default () => <div> {/* The transformed code */}</div>

However, @vitejs/plugin-react could not accept a .md file and I had to use babel to transform the jsx to js.

This is my current configuration file:

plugins: [
  vitePluginDocs(), // my markdown transform plugin
  babel({
    extensions: ['.md'],
    configFile: false,
    presets: [['@babel/preset-react', { runtime: 'automatic' }]],
    babelHelpers: 'bundled'
  })
  viteReact()
]

I want the @vitejs/plugin-react to accept an extra parameter to accept more file's format like this:

plugins: [
  vitePluginDocs(), // my markdown transform plugin
  viteReact({ extensions: ['.tsx', '.md'], })
]

So I can remove the babel from my config.

[LaamGinghong]

By reading the plugin's code, I found that the plugin will only convert mjs | js | jsx | ts | tsx file

[bluwy]

vite-plugin-svelte has a similar feature too that allows specifying the extensions. Probably worth nothing a caveat though: sveltejs/vite-plugin-svelte#60

[LaamGinghong]

@bluwy I think it's a nice feature, so what do you think?

[bluwy]

I'm not familiar with React (nor the vite plugin) so I can't say for sure if there are caveats to this. @aleclarson might know more about it.

[ArnaudBarre]

Hi!
Yes that's a limitation of the current API. Making this change non breaking would make the API unusable so I plan to change this in the next major with #53, hopefully in less than one month