fix(plugin-react): apply babel.plugins to project files only

[aleclarson]

The idea here is to avoid parsing node_modules whenever possible, since that can be expensive in larger projects.

Here's the heuristic I'm using to skip parsing:

 const isNodeModules = id.includes('/node_modules/')
 const isProjectFile = id.startsWith(projectRoot + '/') && !isNodeModules
 const shouldSkip =
   !plugins.length &&
   !opts.babel?.configFile &&
   !(isProjectFile && opts.babel?.babelrc)

For global plugins, set babel.configFile to true and create a babel.config.js file in your project root.

Future

We could detect a babel.config.js file in your project root and enable babel.configFile option automatically.

[aleclarson]

A slight difference in behavior here:

• Linked packages will now have their React.createElement calls reverse-compiled into JSX, so they will also use the automatic JSX runtime.

[benmccann]

Just a heads up - this one will need a rebase

[aleclarson]

If a virtual module wants to avoid being transformed by Babel, it can include /node_modules/ in its module ID.

[jplhomer]

👍 Working well in Hydrogen! Thank you!

[patak-dev]

Thanks for checking this out @jplhomer! Let's release a patch for vite 2.6 and plugin-react with these changes then