refactor(remix-dev/vite): remove redundant jsx and typescript babel plugins

[hi-ogawa]

While investigating mdx hmr in #7954, I noticed that "remix-react-refresh-babel" plugin's transform is receiving already transpiled plain js file, so I think we don't need to add plugins: ["jsx", "typescript"] for bebel transform.

One thing to note is that this is a different from @vitejs/plugin-react, which uses enforce: "pre". In their case, they are intercepting before vite's internal transform, so jsx/typescript handling is required:
https://github.com/vitejs/vite-plugin-react/blob/0cd00a5bf59fe1b326c667efb9c340732c6b0630/packages/plugin-react/src/index.ts#L119-L120

Assuming this first idea is valid, I think remix can then remove remix-react-refresh-babel plugin from child vite compiler since the purpose of child compiler is currently only for extracting exports of route file by getRouteModuleExports and injecting HMR-related code is not necessary as long as code is transformed to plain js.
This could help perf by reducing unnecessary babel transform (though it might not be a significant gain).

Testing Strategy

I think existing tests should be enough to verify the correctness of this idea.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f4f1b06

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pcattori]

I think we still want this change. Can we reopen this PR and scope it down to just this one liner?

[hi-ogawa]

Thanks for re-opening! I updated a PR to include only this change.

Btw, recently macos/webkit CI is often failing with vite-dotenv-test.ts but I'm not sure if it's related to my PR. Is this something I should worry about?

[markdalgleish]

@hi-ogawa I'm looking into that test failure now.

[markdalgleish]

This PR got the test passing: #8177. I've just merged dev into your PR.

[github-actions]

🤖 Hello there,

We just published version 2.4.0-pre.0 which includes this pull request. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!

[github-actions]

🤖 Hello there,

We just published version 2.4.0 which includes this pull request. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!