@vitejs/plugin-react can support more extensions about vite-plugin-react HOT 7 CLOSED

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.

from vite-plugin-react.

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

from vite-plugin-react.

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

from vite-plugin-react.

@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.

from vite-plugin-react.

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

from vite-plugin-react.

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

from vite-plugin-react.

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

from vite-plugin-react.